-
Notifications
You must be signed in to change notification settings - Fork 81
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
Open OnDemand Internal Server Error #184
Comments
It is exactly an expired certificate. IDK if they're publishing new images or not, but if you build the images it should work. That is, what's on Dockerhub is bad, but rebuilding locally with |
I am seeing the same error in Ubuntu 22.04.4. |
Yea the images need to be rebuilt. You can do so locally and it should work. But again, it'll work for x86 machines. If you're on a Mac M1 there's some issue in building that we haven't patched yet. |
Thanks! Rebuilding the images locally worked. However, some functionality fails. When trying to access the Job Composer tab I get:
Any ideas what could be causing this? |
Sorry about that! I see that appear every now and again on some systems for whatever reason. I found that I could exec into the container and install the gem and then it would work.
|
Thanks! That fix worked! |
For those who still don't know how to solve this problem
Additionally, you may encounter websockify compilation failures add a new line before hpc-toolset-tutorial/slurm/install.sh Line 53 in 6baa9a3
|
Can we re-open this issue? JAM2199562's approach does not work for me and the certificate does not update after re-build. Am I missing anything here? Thanks. |
When trying to open the OnDemand URL:
https://localhost:3443
in a browser I get the following error:The error appears in the
ondemand
logs (docker compose logs -f ondemand
) as:I'm running the containers in Pop OS 20.04. XDMoD and Coldfront interfaces work correctly. The Open OnDemand interface had previously worked as recent as 2 weeks ago. I have tried running
./hpcts destroy
and./hpcts cleanup
as well as cloning a new repository and running the setup again. My colleague can also reproduce the error.The fact that it had previously worked leads me to believe it could be an expired certificate maybe?
The text was updated successfully, but these errors were encountered: