discovery 2/3 with 404 Not Found

Support
1

Hi! I’m running a private discosrv and relaysrv. Everything has been working perfectly. However, two new devices do not manage to correctly communicate with the discosrv. They have a 404 not found in the This Device info box under Discovery. Additionally, they can only connect to devices within the same LAN (local discovery). Any ideas how I can get to the root of the problem? Thanks, Jonnie

2

Discovery server only announces 404 when looking up, not when announcing yourself, so you are not hitting the discovery server, you are hitting something else.

3

Thanks for your answer. I don’t really understand it though. What does the 2/3 mean in the web client: When I hover over this with the mouse, it says: global@https://:22026/: 404 Not Found Other devices of mine find it just fine! Any ideas?

4

That’s not a valid discovery server address. To be honest, I have no clue what that is.

5

Hello Audrius,

Thank you for taking the time to answer - and I’m sorry for wasting it too. My attempt to obscure my server’s IP obscured the placeholder too! I’ve found the problem. I was using slightly different global discovery server urls on my different devices. The ones that were working were like this:

https://1.2.3.4:22026/v2/?id=XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX

And the ones which weren’t working were like this:

https://1.2.3.4:22026/?id=XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX

I.e. They were missing the ‘v2’ in the URL.

Thanks again. It’s great software, documentation and support!

All the best,

Jonnie

1 Like
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.