Transport Tycoon Forums

I know this is an old issue but i have not found any solution to the issue.

I have version 13.0 of OpenTTD but my content server is not available to access.
I have tried to disable to firewall, whitelist in firewall, reinstalled steam, reinstalled OpenTTD, downloaded and installed from tt-forum.
I have also tried to use another router, tried the game from different computer with different OS.

Any more ideas to try?

When you say "my content server", do you mean:

1. An OpenTTD game server you're trying to start,
or
2. Accessing the in-game content download server (aka BaNaNaS)?

Hi,

Thank you for responding, i realized as you mention i was a bit wide in my first post.

As you say it is number two, the in-game content server i am trying to access.
I am not able to find any running multiplayer either if it helps you.

Communication with the Game Coordinator works via port 3979 over UDP (inbound + outbound) and 3978 over UDP (outbound). Since you've tried to use OpenTTD on multiple PCs and routers, it might be your internet provider who has blocked these ports.

Hi again,

It might however i have tried to use my phone as a hotspot with the same issue.
I have the same issue with all of my steam games

If it's occurring with all of your games then it is most likely your ISP blocking ports. And if you're trying to do it through a hotspot, definitely most likely because hotspots are usually restricted to just web surfing or low-bandwidth video streaming. Anything which might use a lot of bandwidth, such as video games, are usually discouraged.

Hello, I am facing same problem. I compiled the game (as instructed) running in a docker and now I can see running server in server multiplayer list, but when I try to connect, download of map does not simply start (stuck on 0b). I temporary disabled FW on server side and tested it from 2 locations (also disabled fw, 2 different ISPs). Compiling was done without any incidents (twice - just to be sure).
Have anyone had same problem, or should I report a bug?

I'd say file a bug report, but based on your description I suspect that perhaps something is not quite right with your docker setting or possibly with the ISP that the docker is running on.