IP adress of relay server(s)?

[peterb]

Whenever I try to start a cloud server in public mode I get the following errors:


[3/24/2025 7:02:47 AM] Starting cloud server mode. [peterb]
[3/24/2025 7:02:56 AM] [WARNING] NETWORK: Noble Connect [15068]: Shutting down because of fatal error: Failed to connect to relay server
[3/24/2025 7:02:56 AM] Fatal network engine error occurred. [Failed to connect to relay server]

It started acting like this on Thursday last week.

Starting a server in LAN mode or Cloud in private mode works fine.

Is there anyway one can find out the IP of the relay server? It would be helpful in order to trouble-shot the issue. My current solution is to reboot my PC, but that's a bit of a hassle to have to do that every time I want to start my server.

[Laerun]

Are you using a VPN or perhaps your ISP has some security feature that might interfere with connection?

[LordEntrails]

Well, I've heard the server URI before but I don't recall what it is. But you should be able to do a tracert on a successful connection to get the IPs of all servers in the path.

[peterb]

Are you using a VPN or perhaps your ISP has some security feature that might interfere with connection?

No, I don't use a VPN when running FG. I sometimes do at other times, but that has not been a problem in the past.

[peterb]

Well, I've heard the server URI before but I don't recall what it is. But you should be able to do a tracert on a successful connection to get the IPs of all servers in the path.

Yes, of course. That's a good idea, thanks!

[Lo Zeno]

Whenever I try to start a cloud server in public mode I get the following errors:


[3/24/2025 7:02:47 AM] Starting cloud server mode. [peterb]
[3/24/2025 7:02:56 AM] [WARNING] NETWORK: Noble Connect [15068]: Shutting down because of fatal error: Failed to connect to relay server
[3/24/2025 7:02:56 AM] Fatal network engine error occurred. [Failed to connect to relay server]

It started acting like this on Thursday last week.

Starting a server in LAN mode or Cloud in private mode works fine.

Is there anyway one can find out the IP of the relay server? It would be helpful in order to trouble-shot the issue. My current solution is to reboot my PC, but that's a bit of a hassle to have to do that every time I want to start my server.

I've started to see the same error last Friday. After I hit "cancel" and retry a couple of times, it works and connects. I was trying to figure out if it was my network connection or not, but seeing as you have the same error and it started more or less when it did for me, it might be something related to the cloud servers.

[peterb]

I've started to see the same error last Friday. After I hit "cancel" and retry a couple of times, it works and connects. I was trying to figure out if it was my network connection or not, but seeing as you have the same error and it started more or less when it did for me, it might be something related to the cloud servers.

Seeing that you are UK based (I'm in Sweden) you might be using the same relay server as I, that is: auto.connect.noblewhale.com/eu.connect.noblewhale.com (164.90.201.234), so it might be something going on with that relay server.

[Lo Zeno]

Seeing that you are UK based (I'm in Sweden) you might be using the same relay server as I, that is: auto.connect.noblewhale.com/eu.connect.noblewhale.com (164.90.201.234), so it might be something going on with that relay server.

An update on my situation: I had to demand (unfortunately) to my ISP that they whitelist those URLs and IP address.
At first I thought it was blocked by my antimalware, so I whitelisted them there. It didn't resolve anything so I whitelisted them in my PC's firewall and my router's firewall for good measure, it still got the "Fatal network engine error occurred. [Failed to connect to relay server]" error message in the logs.
Then I tried using a VPN whenever I launch a cloud game, and with that it had no issues at all - that tipped me off. So after a 3 hours long phone call with Virgin Media, I managed to get someone technical to figure out that the eu.connect.noblewhale.com URL was "traffic restricted" (whatever it damn means), and after a long-ish discussion about what I need that for I was assured that it would be unblocked. Seems to have worked and I don't see the issue anymore.

[Moon Wizard]

Wow, great sleuthing. I wish ISPs were a little less vague about what they have done with network traffic or blocked for IPs.

Regards,
JPG