Remote connection problem

[Q-Droid 884]

Do you happen to have a DMZ (or default) server configured in your router? You might want to check because that could explain why all ports are behaving as open. When I try to connect they time out which is the sign of an open port without an active service behind it. A closed port would fail immediately.

 

[Alexmh 2]

Just now, Q-Droid said:

Do you happen to have a DMZ (or default) server configured in your router? You might want to check because that could explain why all ports are behaving as open. When I try to connect they time out which is the sign of an open port without an active service behind it. A closed port would fail immediately.

 

No, trust me I'd wish I had a DMZ option

[Happy2Play 9459]

3 minutes ago, Lessaj said:

At the moment I can only access what you've defined on port 80, I can no longer connect to any random port like I could yesterday. So however you have the rule defined for port 80 seems to work, and should be mimicked for 7920 and 7921.

Yes there is something weird here as it comes and goes for port access where port 80 is the only one shown open currently again.

[Alexmh 2]

6 minutes ago, Lessaj said:

At the moment I can only access what you've defined on port 80, I can no longer connect to any random port like I could yesterday. So however you have the rule defined for port 80 seems to work, and should be mimicked for 7920 and 7921.

just so you'd know, I did nothing but delete port 80 from the camera, and create it in Emby. I didn't even restart the router, because it's not needed on my model, and I run the risk of getting a CGNAT IP. But funny thing ... I DID restart the router just now, because the DDNS still pointed to my camera on port 80, and what do you know, it still points on port 80 to my camera, and not to my Emby server, although I've set the port into Emby server interface.

[Lessaj 301]

I see your IP has changed now from that restart, but yes still only seeing the cameras on port 80. So you tried to set the port 80 rule to send to 7920 on your emby server?

[Alexmh 2]

2 minutes ago, Lessaj said:

I see your IP has changed now from that restart, but yes still only seeing the cameras on port 80. So you tried to set the port 80 rule to send to 7920 on your emby server?

No, I changed the port entirely. Internal-External both on port 80, and also port 80 in Emby server interface.

[Lessaj 301]

Okay that's not really necessary but did you update the IP that the port 80 will be routed to in that rule as well?

[Alexmh 2]

1 minute ago, Lessaj said:

Okay that's not really necessary but did you update the IP that the port 80 will be routed to in that rule as well?

The IP is the same, it won't change, it's binded. (192.168.1.69). So it's the same in the router as it's in Emby app, which detects it automatically anyway.

[Q-Droid 884]

Are you certain that Emby is listening on 7920 and 7921?

[Alexmh 2]

1 minute ago, Q-Droid said:

Are you certain that Emby is listening on 7920 and 7921?

No, I've just said I changed it to 80 for testing purposes. At least on http, I don't care about https at the moment. So Emby listens to port 80.

[Lessaj 301]

4 minutes ago, Alexmh said:

The IP is the same, it won't change, it's binded. (192.168.1.69). So it's the same in the router as it's in Emby app, which detects it automatically anyway.

So you're running your cameras off the same host as your emby server?

[Alexmh 2]

6 minutes ago, Lessaj said:

So you're running your cameras off the same host as your emby server?

No. My network setup is the following (sorry for my paint skills):

[Happy2Play 9459]

20 minutes ago, Q-Droid said:

Are you certain that Emby is listening on 7920 and 7921?

Accord to the server log posted it is.

But would need to see new server log for port change.  But there is a routing issue somewhere as in the ISP route if not changing from camera to Emby but that should come back to the portforwarding rule.

[Lessaj 301]

1 minute ago, Alexmh said:

No. My network setup is the following (sorry for my paint skills):

 

Okay but if you're trying to route your exposed port 80 to your emby PC (now also using port 80 locally) instead you would have to change the internal host IP in the rule that you're using for port 80, that's why the cameras are still what's coming up.

[Alexmh 2]

2 minutes ago, Happy2Play said:

Accord to the server log posted it is.

But would need to see new server log for port change.  But there is a routing issue somewhere as in the ISP route if not changing from camera to Emby but that should come back to the portforwarding rule.

Ok I will resend the new logs.

[Alexmh 2]

1 minute ago, Lessaj said:

Okay but if you're trying to route your exposed port 80 to your emby PC (now also using port 80 locally) instead you would have to change the internal host IP in the rule that you're using for port 80, that's why the cameras are still what's coming up.

Ok let me make it more clear:

Camera IP: 192.168.1.111 (Port opened: others, not 80)

Emby/PC IP: 192.168.1.69 (Emby port: 80)

Gateway: 192.168.1.1

I think I know the problem, now I see the delete command was not applied for the camera port, only the addition of the new port for the emby. The router can't do two operations at once even if they are in the same window. 

I'll come with updates.

 

[Alexmh 2]

Ok, now when I enter DDNS:80, and WANIP:80, it redirects me to Emby, but only on LAN.

Also here are the new logs.

embyserver-63860751370.txt hardware_detection-63860749193.txt embyserver (1).txt

[Lessaj 301]

Okay I suspected that 192.168.1.111 was the cameras just cause it was the first rule you had.

So if you were trying to expose emby on port 80 on your ISP router you would need to create a rule for internal host IP 192.168.1.69, TCP protocol, external port number 80, internal port number 80, and external source port can be 0 or empty since that would be random anyway. No other rule can use external port 80.

At the moment I can connect to your port 80 with telnet, but no web page loads in my browser anymore.

[Alexmh 2]

2 minutes ago, Lessaj said:

Okay I suspected that 192.168.1.111 was the cameras just cause it was the first rule you had.

So if you were trying to expose emby on port 80 on your ISP router you would need to create a rule for internal host IP 192.168.1.69, TCP protocol, external port number 80, internal port number 80, and external source port can be 0 or empty since that would be random anyway. No other rule can use external port 80.

At the moment I can connect to your port 80 with telnet, but no web page loads in my browser anymore.

There is no other rule using port 80 other than Emby as this moment.

[Q-Droid 884]

Port 80 isn't responding and neither are any of the other ports discussed in this thread so far.

 

[Alexmh 2]

4 hours ago, Q-Droid said:

Port 80 isn't responding and neither are any of the other ports discussed in this thread so far.

 

Yep, probably because I went to sleep. I'll write when I'll get back from work.

[Luke 40144]

On 9/1/2024 at 1:18 AM, Alexmh said:

Yep, probably because I went to sleep. I'll write when I'll get back from work.

Hi, let us know how this goes. Thanks.

[Alexmh 2]

10 hours ago, Luke said:

Hi, let us know how this goes. Thanks.

Hey! Of course, I will reply here as soon as there is a change or I give up  Thanks again for everything!