Responses (2)

A

abqnm

They did publish them... For some reason the link just leads to their support homepage now. Here was the link, just in case it starts working again. [https://support.ring.com/hc/en-us/articles/205385394-What-Ports-do-I-need-to-open-in-my-firewall-for-Ring-Doorbells-and-Chimes-](https://support.ring.com/hc/en-us/articles/205385394-What-Ports-do-I-need-to-open-in-my-firewall-for-Ring-Doorbells-and-Chimes-)

0

•

19-06-2019 13:23:42

•

Reply

B

BitzerMaloney

Yeah I did find this, but when I went to the page it said I was not authorized to access the article. I can view other articles fine.

0

•

19-06-2019 23:27:00

A

abqnm

> @BitzerMaloney wrote: > > Yeah I did find this, but when I went to the page it said I was not authorized to access the article. I can view other articles fine. Yeah that was weird to take it offline to update it, but hopefully they update it fast because I reference it about twice a month, inevitably, when dealing with client issues.

0

•

19-06-2019 23:50:05

W

whiteswan

had cause to ring up Support yesterday and was told you no longer have to open any ports for the doorbells. I am having problems with my RVD 2 and a new tp link mesh system - so I asked about opening ports and was told that's a thing of the past. Maybe that's why they took it down ? I have a call booked with a level 2 tech on Tuesday so I will ask him. Dave

0

•

30-06-2019 16:26:31

A

abqnm

> @whiteswan wrote: > > had cause to ring up Support yesterday and was told you no longer have to open any ports for the doorbells. > > > > I am having problems with my RVD 2 and a new tp link mesh system - so I asked about opening ports and was told that's a thing of the past. > > > > Maybe that's why they took it down ? > > > > I have a call booked with a level 2 tech on Tuesday so I will ask him. > > > > Dave NAT has generally made port forwarding/triggering unnecessary and a thing of the past. Most consumer routers will have zero problems with ports. However, if you have a dedicated hardware firewall, that can be a different story, but usually there's a way to whitelist entire devices (by MAC or IP) so that they are exempt from the firewall, again making port opening irrelevant. But there are some limited cases where you may need to open specific ports in the firewall for each Ring (or most any other IoT device) device. However, your consumer TP-Link mesh router/wifi is not going to be one of them. If you want to discuss your particular issue further, I'd suggest creating a new post with the problems you're having, the devices and networks you're using when having the problems, etc. so as not to clog up this port-related thread with a separate issue. I don't work for Ring nor are a moderator so I can't just move this myself. But if you post a new topic I'll see it, even if it takes me a couple hours. If you're using a PC to post here, you can tag me specifically which will email me. Tag me by typing @abqnm and as you type it should give you a drop down to choose my username. This won't work on mobile though, so if on mobile, I'll just see your post when it shows up in the rss feed.

3

•

30-06-2019 16:46:57

M

Metalshark

Please can you get them to update it again with why there is outbound traffic to port 8108? The support team on live chat and Twitter are somewhat missing the point: https://twitter.com/ring_uk/status/1560334864947331072 Thank you

0

•

18-08-2022 20:38:11

S
SBCmac
I have gone through Ring's Support Article on the ports to open up for Ring devices. And there seems to be missing Firewall Rules specified in the below support document. I keep having to open all ports in order to get my Ring Devices to work. Any ideas? https://support.ring.com/hc/en-us/articles/205385394-What-Ports-do-I-need-to-open-in-my-firewall-for-Ring-Doorbells-and-Chimes-
0
•
27-05-2021 21:10:35
•
Reply