search

ttalvitie / browservice

Browservice: Browse the modern web on historical browsers
MIT License
1.08k stars 32 forks source link

Browservice doesn't work without NAT Loopback. #83

Open vladger opened 1 year ago

vladger commented 1 year ago

Browservice requires NAT Loopback to be enabled on my router port forwarding settings, if disabled, it will show connection or timeout error.

ttalvitie commented 1 year ago

From the limited information available, my guess is that you are exposing Browservice to the internet (that is, anyone can connect to it using address http://[YOUR IP]:8080/). This is VERY DANGEROUS, as stated in the README:

WARNING: Binding to 0.0.0.0 may allow unauthorized users to connect to the server. Giving untrusted users access to the server is very dangerous; for example, they can access all the user accounts on websites to which you have logged in using Browservice. To avoid this, restrict the incoming connections to isolated local networks using a restrictive listen address and/or a firewall.

(I'm guessing this because this is the only way I think NAT loopback could help, if you connect to Browservice running in your NATted local network from the same network using your public IP. In the normal usage, you would connect it using the local IP, and make sure that Browservice is not accessible from the outside.)

If I guessed wrong and you are doing something else, then I need more information about your networking setup to be able to help. At least, it would be good to know which address do you use to connect to Browservice on the client browser.