-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker build not working #286
Comments
Hello! I forgot to death - the Dockerfile has not been updated in a good while! If you're interested, the real working build instructions that are always up to date are found in the .yml files, e.g. Linux_build.yml. I'll take a look at Dockerfile later |
Hey @hpx7 , take a look at the new Dockerfile. Cheers! |
Thanks, it builds now but fails to run with
Is it possible to run without fuse? |
Unfortunately
Does this happen with the new Dockerfile (so the line needs to be added there)? Or do you maybe have your own? |
It happened with the new Dockerfile, but was able to get it to start with your suggestion:
Is WebRTC required to connect from the web portal, or are websockets supported as well? I'm running it an environment where port ranges (e.g. |
I see, we might need to update it.
WebRTC is necessary from the Web to establish connection with any game server. WebSockets are still used to communicate with the signalling server that lets us initiate the WebRTC connection. If you only plan to support several web clients at most, consider setting:
And then only exposing ports 9000, 9001, 9002, 9003 and 9004. |
I tried updating
But I don't think the configuration was correctly applied:
|
Check if the new Dockerfile works any better. It's copying the config into The next server build will also allow muxing on a single UDP port. (i need to deploy it first tho) |
I tried the latest but it still logs |
Thank you, I just found a bug that caused some settings to not be applied on startup. This will be fixed in the next update. |
Awesome, let me know when the next release is cut and I'll test it out! |
This uses the lowest possible Ubuntu version.
The new version is live.
Let me know if the config loads correctly as the Docker server had problems locating
If it doesn't, try renaming |
Startup failed with
I tried renaming it to
|
Looks like there was just a comma missing in Now I'm having issues connecting to the server:
When I try to connect to it from |
Thanks for the catch - fixed the comma! That's already some progress.
Are you sure your Docker server is visible from the server list here? (the one If it's missing, it means it is not registered with the signalling server and has no way of accepting WebRTC connections - even if you use a direct browser link. Try double-clicking your server from the server list. What about the native client by the way? Does it connect? Also forgive me for all the chaos - you're actually one of the first testers of the Docker build - you're doing me a favor! |
I tested the current
Also make sure any other official server works from your browser, e.g. https://hypersomnia.io/game/pl:1 |
I see the server on the list, but still can't connect I can confirm that https://hypersomnia.io/game/pl:1 works for me in my browser |
Here's a link to the server logs in case that's helpful: https://drive.google.com/file/d/1T9X350mc9ydjSH4YBcaXdKUnAttqG_R5/view?usp=sharing I am using the default codebase from |
As far as I can tell all currently running dedicated servers are port-preserving cones, so the internal port matches the external port (incl. the other How about the native clients? Can they connect? If not, then it's almost surely a problem with how |
I think even if native clients could connect, the WebRTC backend might require that the external ports aren't random so it performs the STUN mapping and SDP exchange without issues (it has to even for public servers without routers). Definitely do try to map internal |
A small update: the server now uses JSON instead of Lua files, but this is already reflected in the latest |
Running
docker build -t hypersomnia
onmaster
fails with the following error:The text was updated successfully, but these errors were encountered: