Open andothomas opened 11 months ago
Was able to fix the authentication issues, didn't realize I had the GitHub pem file double mounted...removing mentions of ./file.pem:/config/file.pem:z
seemed to do the trick. Along with removing empty pem files that popped up (perhaps related to double mounting).
It would likely benefit future users if these instructions were altered to say something like "the default configuration mounts the config directory (code here), so if the pem file is placed in the config directory, it does not need to be explicitly mounted".
However, I am still having to disable gzip. It appears that it's only an issue when using podman since I didn't have any such issues with docker compose.
Was able to set up, run self-hosted, and view the login with GitHub page it over HTTP, but when attempting to set up HTTPS to allow GitHub authentication to work, I ran into two issues. I'm presented with a blank page and either a JS or CSS file (or both) appears to have not loaded, though loading a file by navigating to it in a web browser directly works fine. On Chrome I get a console error of
ERR_HTTP2_FRAME_SIZE_ERROR
and Firefox aNS_ERROR_NET_PARTIAL_TRANSFER
. Implementing a workaround reveals the second issue of going back to the login page after the authentication flow completes (also observed before setting up HTTPS). Here is the current setup:docker-compose.yml:
Also tried
8443
under ports for the frontend.codecov.yml:
Came across this answer on Stack Overflow that seems to describe a similar issue. Disabling gzip in the nginx config of the frontend container while it is running seems to fix this issue, but I have to do this manually every time I run the self-hosted docker compose file:
podman exec -it -u 0 <frontend-container> sh
gzip on
togzip off
nginx -s reload
Though even after this workaround, I'm still having issues with GitHub authentication bringing me back to the
Login via GitHub
page after the authentication flow should be complete. Requests on this page to/internal/user
return a 401 saying "Authentication credentials were not provided", and the GraphQL GitHub user object request to/graphql/gh
returns{"data": {"me": null}}
. Not sure if I have something configured improperly, but when I observed this same behavior over HTTP I thought the issue was the combination of no SSL and using a custom domain...now I'm not so sure. Any insight would be greatly appreciated!