Seite 1 von 1

2-FA update: cannot connect to the server

Verfasst: 9. Feb 2023, 13:53
von escrime
The release notes for the Android app has been requesting that I edit the server entries by reconnecting using the button on the "Edit server" page. When I tap "Connect to Server and Save" I get "Error 404: Server not Found". I can find nothing in the help about this nor whether I now need to add 2FA to the server and how to do this. Hopefully someone can help!

Re: 2-FA update: cannot connect to the server

Verfasst: 9. Feb 2023, 14:46
von Martin
2-FA is only required if you run a Synology or QNAP NAS.
If you see "404: Server not found" please verify that the server url is valid and can be reached.

Are you connecting to a local server in your LAN or from outside to your public ip address?

Re: 2-FA update: cannot connect to the server

Verfasst: 10. Feb 2023, 13:35
von escrime
Thanks Martin. The server is on the local LAN.

Re: 2-FA update: cannot connect to the server

Verfasst: 10. Feb 2023, 13:46
von escrime
Now fixed. The IP address had changed (thought I had fixed it..) but now I know 2FA not required, it is working :)

Thank you!

Re: 2-FA update: cannot connect to the server

Verfasst: 10. Feb 2023, 14:37
von Martin
Glad you got it working again!

Martin

Re: 2-FA update: cannot connect to the server

Verfasst: 4. Jul 2023, 18:08
von escrime
Hi Martin,

For some reason the app now will not start the server remotely. The IP has not changed and if I start the server manually the app finds it. I am specifying port 7782 after the IP address. Any idea why please?

Re: 2-FA update: cannot connect to the server

Verfasst: 5. Jul 2023, 10:09
von Martin
You say "remotely": This usually doesn't work with a SoHo router. These routers can't broadcast to your local network. And that is required for Wake-On-Lan.

Background: The router has a mapping between IP address and physical MAC address. So the router knows where to send an IP packet. This mapping is deleted after 10-20 minutes when the server is switched off. Now the router does not know where to send the packet and shouts into the network: Who is IP address xxx? And nobody will answer.
Therefore, a WOL packet must be sent to everyone (i.e. as a broadcast). And SoHo routers do not allow that.

The mean thing is, that it mostly works during testing, because you are within the 10-20 minutes range. After that it doesn't work anymore.

The only reliable solution is another computer, which takes over the sending of the broadcast. This can be e.g. a Raspberry Pi, for which there is the software here: https://www.green-it-software.com/wake- ... pberry-pi/

Regards
Martin

Re: 2-FA update: cannot connect to the server

Verfasst: 16. Jul 2023, 17:14
von escrime
Hi Martin,

Thanks for your reply and sorry for my delay in replying.

When I say 'remotely' my phone is on the same LAN and the server hibernates so I am probably using the term incorrectly. It always used to work, though the server took some minutes to wake up and respond. I was just wondering what might be the cause, because the IP address of the server is fixed so I am not sure why I cannot wake the server from the app.

Kind regards,

Andrew

Re: 2-FA update: cannot connect to the server

Verfasst: 19. Jul 2023, 21:21
von Martin
What is your server for a machine?

Re: 2-FA update: cannot connect to the server

Verfasst: 30. Jul 2023, 17:06
von escrime
HP MicroServer running WHS 2011.
The IP address is correct. When I start it manually the app then finds it once it has woken from hibernation . It was working, so I am not sure why it is not now.

Re: 2-FA update: cannot connect to the server

Verfasst: 31. Jul 2023, 09:19
von Martin
Then please connect while it's running , open console, go to tab mobile devices and check that wake-up is enabled.

Re: 2-FA update: cannot connect to the server

Verfasst: 1. Aug 2023, 14:04
von escrime
That has fixed it! I wonder why it changed. I found two entries for the phone, so I deleted the older one. The more recent did not have wake-up enabled.

Many thanks Martin.