-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
After update docker shows ombi running but unable to load the page #5132
Comments
The fact that you are rolling back to another image but running the same Ombi version (4.44.0) implies this has not been cause by Ombi? I'm not sure what the problem would be here as it's complaining about a SSL error with your MySQL database. |
You may need to update your version of mysql. This fixed it for me. I am using the linuxserver.io ombi container and the example from the ombi website. Make a backup of your data and change the image from mysql to mariadb. Worked without a hitch for me. I am assuming the issue was probably outdated openssl version on mysql container. Hope this helps. OpenSSL 1.0.2k-fips 26 Jan 2017 - mysql:5.7 container OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) - ombi container |
This exact same issue was happening to me, switching to a mariadb container, did solve the problem. |
Thanks for the reply's I think youre right the mysql 5.7 img is using an older version of openssl thats causing the issue, I originally followed the guide at https://docs.ombi.app/info/docker-containers/#docker-compose. I'm still a bit green messing with docker sorry if im missing something simple, I tried to change out the line in my docker-compose from image: "mysql:5.7" to image: lscr.io/linuxserver/mariadb:latest but now im getting a different error in the logs and ombi doesnt load in the browser: Unhandled exception. MySqlConnector.MySqlException (0x80004005): Table 'AspNetRoles' already exists |
That error indicates that Ombi is attempting to run a migration on your database now. That means that it’s either missing data or tables so it’s on a bit of a corrupted state… |
I changed my image to: |
I also had this error due to mysql:5.7 in my compose file from the example docs. Upgrading it straight to 'latest' threw errors about not being able to upgrade this version, so I backed off to mysql:8.2 I finally tried 8.4.0, but that also errored saying unable to upgrade from this version (8.3). That's where I've left it for the time being. |
Thanks, this ended up being my fix for now as well. Im trying to get mariadb to work but some reason had issues with root password not working or some corruption of the db. Changing out mysql:5.7 to mysql:8.2 and everything working on the latest ombi img. |
This worked for me as well in my docker-compose file except my version was 5.1 or something. |
How can I update mysql? Isn't it inqluded with the docker image and should be updated in the provided image? For me It's a first time setup, and I'm getting similar errors. |
In your docer compose file, replace the line: image: mysql:5.7 With image: mysql:8.3 |
Summary
After updating docker to the latest image I'm unable to access ombi. Looking at the logs looks like like ombi can no longer connect to mysql maybe? rolling back to the previous img development-v4.44.0-ls399 fixes the issue
Ombi Version
v4.44.0
What platform(s) does this occur on?
Docker
What database are you using?
MySQL
Relevant log output
The text was updated successfully, but these errors were encountered: