Closed ZelphirKaltstahl closed 1 week ago
Not found
Have you copied the static
directory into the container's filesystem?
2024/07/03 23:59:48 http: TLS handshake error from 172.17.0.1:36444: remote error: tls: bad certificate
Please ignore this, it's just a warning that indicates that the browser rejected the certificate. Unfortunately, it cannot be easily suppressed, since it's generated by Go's HTTP code.
Closing. Please reopen if including the static
directory doesn't fix your issue.
Saw your response. Thanks for your suggestion! Need more time to test things. Will post here, if I figure something out.
The 404 disappears, when I have the static
directory. Thanks!
I built galene inside a docker container, using the build commands mentioned in same installation guide at https://github.com/jech/galene/blob/master/INSTALL#L5. I am starting the container like this:
I have an entrypoint looking like this:
The installation guide at https://github.com/jech/galene/blob/master/INSTALL#L47 says I should be able to connect to galene, but what actually happens is this:
The built
galene
binary is in that directory andgalene
seems to run, but contrary to simply being able to visit it in the browser at https://localhost:8443. I do see the expected untrusted certificate warning of my browser. However, when I add an exception, I get to a page that says:Not found
While I see the following in the logs:
On https://galene.org/INSTALL.html it says:
But this seems to be wrong. The TLS certificate generated cannot be used, because it is somehow "bad". Or is galene simply refusing to serve, when using a self-signed cert? But then Why generate one at all?