Remote web servier issue over lan but not wifi

[cuda1337]

I was having lots of lag and difficulties watching camera's on my remote web server, so I decided to plug the computer in via ethernet rather than letting it run via wifi.

The cameras seem to work better on the desktop (although, I don't know why...). But now the remote server isn't accessible anymore. When I run the wizard with the pc plugged in via ethernet, it isn't able to complete one of the last steps. But as soon as I unplug the ethernet cable and am connected via wifi, it works no problem.


Any ideas on what I need to do to fix this?

[BruceH]

Check the IP address of your ethernet card on your desktop, is it possibly set to the same address as your BI server? What step does the wizard fail on?

[TimG]

I'm guessing the IP address is different with the pc on wifi and then ethernet and the router has the IP for the pc on wifi. It could be as simple as checking the router settings for port forwarding to the pc on wifi, and changing it to the pc's ethernet IP address.

Wow, BruceH on a similar thought path

[cuda1337]

Thank you both, I'll take a look at that and see if I can make some headway on the problem.

[cuda1337]

Check the IP address of your ethernet card on your desktop, is it possibly set to the same address as your BI server? What step does the wizard fail on?

Ok, I'm actually in person at the computer now, trying to troubleshoot and fix it.

Some of this networking stuff is above my head, but I'm going to do the best I can here.

The IPv4 address of my network card ends in a .68.97.

This is the same as the local, internal lan address in the web server lan address settings in blueiris.

The remote, external IP address in the web server settings is different, ending in 81.104.


When I check my IP address on the internet, while plugged in via ethernet, or unplugged and connected via wifi, I get the 81.104 IP address as well. As soon as I unplug the ethernet cable, the web server starts being accessible.

Ok, whats' weird is, after plugging the ethernet cable back in, I ran the setup wizard, and this time it went through completely without fail. However, I do remember a few days back when I was trying this, the web server remained available for a short period of time after going from wifi to ethernet, and then went down, not to be accessible again while plugged in via ethernet.

I'm going to give it an hour or two and see if it stays up this time, and then report back with my findings.

[Shukhrat]

I’ve had a similar issue where plugging in via ethernet caused some weird conflicts with my wifi connection. What worked for me was disabling the wifi adapter when I switched to ethernet, just to avoid any network confusion. Also, make sure both connections aren’t trying to use the same IP or gateway—sometimes they get mixed up. If you’re still having trouble, it might be worth checking the server settings to ensure it’s set up to allow connections from both interfaces. It’s a bit of trial and error, but usually, it’s something small like that causing the issue.

[cuda1337]

Ok so my server was working great for a few weeks and then this morning the computer restarted. No biggie, restart blueiris. Web server isn't working again.


No idea why or what a computer restart would change?


When I run the remote access wizard it keeps failing on the last step that performs a final test of your networking and routing.

[TimG]

Does the BI5 pc have a static IP address ?

[cuda1337]

It doesn't. Funny thing though. I set it to static, and then set it back to Dynamic, and it started working again... so it's something to do with that I'm guessing.

[TimG]

As I understand it, you will need to set a static IP address for the BI5 PC. If you have set up port forwarding in your router for remote access, it will point to that internal LAN static IP address and it won't expect it to change. If you reboot the BI5 PC and it doesn't have a static IP, then the router will hand out a DHCP dynamic automatic IP address and your remote access will not work. I think by setting the BI5 PC to static and back to dynamic you may somehow have got the correct IP address. I suggest setting the BI5 PC with a static IP with the known IP that it has when its working !

Normally you would look at the router settings to see which addresses are handed out by the DHCP system. If it is a range like 192.168.0.10 to 192.168.0.50 then you would avoid that range when choosing static IP's. You could for example put the BI5 PC on 192.168.0.100 but you would have to ensure the router had that IP for the port forwarding - or run the Wizard to try to set it up automatically. I never had much luck with automated router settings, so I tend to do it all manually.