search

juharris / switch-remoteplay

NOT AN OFFICIAL NINTENDO PRODUCT - Control your Switch remotely (no hacking required)
https://jubuntu.eastus.cloudapp.azure.com/
MIT License
288 stars 18 forks source link

Client won’t connect? #45

Open i-02 opened 3 years ago

i-02 commented 3 years ago

Hi, first of all thank you for creating this awesome tool. I’m trying to connect through the https://jubuntu.eastus.cloudapp.azure.com/ client, but it just says it’s attempting to connect and nothing ever happens, not even an error message. I have the server seemingly working; my Switch recognizes/pairs my Raspberry Pi as a pro controller. The last line of output on the console for the server is “root _reply_to_sub_command::295 INFO - received output report - Sub command SubCommand.SET_PLAYER_LIGHTS”. I’m not sure how to go about even just inputting the ‘a d’ ‘a u’ style commands into terminal to test it out.

Again, thanks and I apologize because I’m sure I’m just making a dumb mistake. I could be using the wrong IP address, but I used curl ifconfig.me to get what I believe is the correct one.

juharris commented 3 years ago

Thank for the appreciation and for trying out the tool? Do you see anything interesting in the Console in the browser? Usually you press F12 to open it.

juharris commented 3 years ago

Looks like https://ifconfig.me/ gives your public address. That might not work on your local network. I assume the device you're looking at that browser page in is on the same network as a Raspberry Pi? You should try with your local IP address for your Raspberry Pi. You can enter hostname into the command line on your Raspberry Pi and it should give you a name that you can use on your local network.

If you do want to use your public IP address because the Raspberry Pi is on a different network from your browser then you'll have to look into exposing your Raspberry Pi publicly so you'll have to check your router settings for how to expose ports publicly.

I know I should document this stuff but I'm not too sure of the best way to do it by myself so that's why I haven't.

i-02 commented 3 years ago

That’s totally alright, I really appreciate you responding to these issues! You’re right that my client device is on the same network, although I did also try with what I believe was the correct private IP and ran into the same problem.

I’m not at home right now but when I am I’ll double check the private IP and also take a look at the browser console.