Skip to content

Add HTTPS #12

Open
Open
@JamesDAdams

Description

@JamesDAdams

Hi,

I added the https but there is no parameter to activate it for this container...

Mu docker container:

docker run -d --name quakejs
-e SERVER=quakejs.domainename.com
-e HTTP_PORT=80
-p 10113:80
-p 27960:27960
-l traefik.enable="true"
-l traefik.http.routers.quakejs.rule="Host(quakejs.domainename.com)"
-l traefik.http.routers.quakejs.entrypoints="websecure"
-l traefik.http.services.quakejs.loadbalancer.server.port=80
treyyoder/quakejs:latest

Sans titre

( i replace my domaine per domainename ^^)

Activity

purvaldur

purvaldur commented on Aug 20, 2021

@purvaldur

Bump - I encountered this issue as well. No idea how to workaround

morganzero

morganzero commented on Sep 6, 2021

@morganzero

BUMP!

samkasman

samkasman commented on Feb 5, 2022

@samkasman

Also trying to figure out how to get it to work via Traefik/HTTPS, no luck

treyyoder

treyyoder commented on Aug 30, 2022

@treyyoder
Owner

Have you tried a reverse proxy? Like nginx?

morganzero

morganzero commented on Aug 30, 2022

@morganzero

Have you tried a reverse proxy? Like nginx?

I've tried Traefik Reverse Proxy

stp14

stp14 commented on May 17, 2023

@stp14

Bumping this! I also have tried with nginx and have the same issue. I went into the code (ioquake3.js and ioq3ded.js) and changed http to https where it sets the url variable - lines 15227 and 15277 in ioquake3.js, and lines 9532 and 9404 in ioq3ded.js

Doing that gave me the following error related to ioq3ded.js under the ----- FS_Startup ----- header:
TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"

On the nginx side, I've tried adding proxy_set_header X-Forwarded-Proto https as well as a sub_filter to try to force https with no luck.

realies

realies commented on Dec 24, 2023

@realies

@stp14, please try the changes in #24. This should allow for an easy reverse proxy setup.

madsboddum

madsboddum commented on Mar 15, 2024

@madsboddum

Encountered this yesterday as well.

neonwatty

neonwatty commented on Nov 14, 2024

@neonwatty

There is also a rundown of how to do this with the un-dockerized version. See under Running Secure Servers (Content, Dedicated, and Web) Quick-Start.

neonwatty

neonwatty commented on Dec 2, 2024

@neonwatty

I did a little more digging and - using a fork of the quakejs branch above - built this new pattern for running a dockerized quakejs via https.

It requires no manual reverse proxy setup / configuration or ssl cert setup (these are performed automatically), and works with any self/hosting provider.

You can try it out at this example url

https://kamal-quake.xyz

You can find more details here to see if this pattern works for you.

I am still working out a final issue: proper setup / routing of the (secure) web socket.

The lack of working web socket causes the "awaiting challenge" screen. You can create a multiplayer game from the menu, but can't join one in progress.

AlinGheaja

AlinGheaja commented on Feb 12, 2025

@AlinGheaja

any progress adding https to docker and game ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Participants

      @treyyoder@madsboddum@realies@purvaldur@neonwatty

      Issue actions

        Add HTTPS · Issue #12 · treyyoder/quakejs-docker