search

t2t2 / obs-tablet-remote

Tablet optimised OBS Remote
http://t2t2.github.io/obs-tablet-remote/
MIT License
428 stars 129 forks source link

I can localhost into my PC, but using the IP doesn't work #11

Open yashendra2797 opened 7 years ago

yashendra2797 commented 7 years ago

Hey there! I just cam across this tool and set it up. First everything went amazingly awesome, however on trying the same on my iPad, using localhost (obviously) did not work. Realizing my error I tried my local IP address and then the external one. I even checked if the port was open (it was). However, the site refuses to connect even on my own PC with an IP address, working only via localhost. Could you help me out?

Thanks!

PS: I apologize if this was the incorrect place to post this.

hengie commented 7 years ago

I have the same error. Please help I need to use this for streaming.

sirkkalap commented 7 years ago

You need to be inside a network that can reach your PC.

a) There must not be a firewall between tablet and PC, including the PC internal firewall. b) There must be a route from tablet to PC, so use LOCAL LAN OR a public IP in the PC - warning public IP is dangerous - c) You must understand what it means security wise to make your PC IP public in b. Hint: it means anyone can call your PC from the internet. 🥇 :)

yashendra2797 commented 7 years ago

a) There must not be a firewall between tablet and PC, including the PC internal firewall.

You mean I have to disable Windows Firewall?

b) There must be a route from tablet to PC, so use LOCAL LAN OR a public IP in the PC - warning public IP is dangerous -

I DID use Local LAN. Which is why its weird why I can't connect.

c) You must understand what it means security wise to make your PC IP public in b. Hint: it means anyone can call your PC from the internet. 🥇 :)

Its an internal network. Port forwarding is on. I can call the port from my MacBook Air. Just can't connect to the server.

EDIT: I just realized that this might be construed as passive aggressive, in which case I apologize, that isn't my intention 😄

Avatar4pro commented 6 years ago

connecting and nothing happens :/ oh, server not reachable after 1 min

kaimi commented 6 years ago

Check if your PC has multiple IPs, and which OBS binds to. That should be the one the websocket plugin listens on.

Settings → Advanced → Network (at the bottom) → Bind to IP. Try messing with the settings down there as well.

Does sound firewall related to me, though. I have no idea how the Windows firewall works (using mostly linux), but you should be able to add an exception for OBS somewhere.

Last thing that comes to my mind right now is trying another port. Maybe something else is already listening on your local IP and the websocket plugin port?

geriatricginger commented 5 years ago

Was this ever sorted out for you guys? I am getting this. I have all ports forwarded, opened up, firewalls down, etc. I can "localhost" from the page and get to it, even with my phone, but neither phone nor PC will reach it by IP address, or outside the network. websocket is running and connected, listening to port 4444. 4444 is forwarded in both modem and router, and Norton AV.

yashendra2797 commented 5 years ago

Nope.

geriatricginger commented 5 years ago

So I sorted mine out. Apparently, Comcast/Xfinity was blocking 4444. Changed to a different port and can now connect fine.

rodrigograca31 commented 3 years ago

If anyone is using Linux (Mint) and having problems like I do here is the fix:

It opens all ports. be careful. dont do DMZ or other stuff.....

sudo iptables -P INPUT ACCEPT                                                                                     
sudo iptables -P OUTPUT ACCEPT
sudo iptables -P FORWARD ACCEPT
sudo iptables -F
kaimi commented 3 years ago

In case that wasn’t obvious, do not do that ↑. It basically disables the firewall entirely.

Also do not just use random commands you found somewhere. In this case instead of allowing incoming traffic to port 4444 it sets the default policy (= when no rules apply) to allow all traffic, for incoming packets, outgoing packets and forwarding. Then it deletes all rules in all chains. You know, just in case there was a rule explicitly forbidding port 4444.

Instead please do it properly. The easiest way is probably to use whatever frontend your OS provides, or at least spend 5 minutes googling how iptables works. Here’s a random front page hit.

rodrigograca31 commented 3 years ago

@kaimi none of that worked for me. I had 4444 allowed and I even disabled my firewall with "sudo ufw disable" but seems to be some other thing blocking it which those commands solved.

also that doesnt stay across reboots so you will need: iptables-persistent too

I was providing 1 potential solution! of course you shouldn't run random commands from the web unless you know what they do.