I don’t think it’s working… I don’t have problems with logging in, but I also don’t have access to the wizard. https://mydomain.com/ombi/Wizard redirects to https://mydomain.com/ombi/, I can log out and log in but the only thing I’m getting is the gray background, the navbar at the top, and the orange stripe. This was without the rewrite rules.
!
Hmm, this is both strange and frustrating. Will you run upgradeOmbi one more time and try again? Additional to this, it should have the logo as Ombi and not Plex Requests. Are you on a current version of QuickBox?
I changed Ombi’s Application Name, you can change the Ombi in the top left corner to anything you want.
Ran sudo upgradeOmbi, here’s the log from the last two runs:
[info] Verboity level: [none]
[debug] Update script running as: root
[info] Ombi service file for systemd found…parsing…
[info] Parsing complete: InstallDir: /opt/Ombi/, User: ----, Group: ----
[info] Downloading Ombi update…
[info] Checking for latest version
[debug] latestversion: 3.0.2776
[debug] jobId: jqegwte5rpdg49ed
[debug] version: 3.0.2776
[info] Latest version: 3.0.2776…determining expected file size…
[debug] size: 47271237
[info] Expected file size: 47271237…downloading…
[info] Version 3.0.2776 downloaded…checking file size…
[info] File size validated…checking Ombi service status…
[info] Ombi is not active…installing update…
[info] Update installed…setting ownership…
[info] Ownership set…not starting Ombi
[info] Cleaning up…
[info] Update complete
[info] Verboity level: [none]
[debug] Update script running as: root
[info] Ombi service file for systemd found…parsing…
[info] Parsing complete: InstallDir: /opt/Ombi/, User: ----, Group: ----
[info] Downloading Ombi update…
[info] Checking for latest version
[debug] latestversion:
[debug] jobId:
[debug] version:
[crit] Build version does not match expected version
Pretty sure this means it’s up to date. localhost:5000 also says it’s up to date. Version 3.0.2776
Can I PM you so I can check this on your server? 3.0.2328 is the latest version
Sure. ____
Just wanted to add that I’m also having the same issue as kilometers. Never had an issue until recently. I’m now seeing the Ombi page with only the gray background. My server is on a QB subdomain and my cert has expired.
@JMSolo Please let me know if you need another server to test. Thank!
Yeah, this appears to be an issue with Ombi using subdomains on a reverse as regular domain.com have no problem. @j0hnwick, what version of Ombi are you using? Also, I am sure it already is populated, so in the meantime, it may result in needing to access via http://do.main.com:5000/ombi until I figure out a proper reverse for Ombi.
Hi ! Same issue here, server is on a subdomain, just updated manually Ombi and now i can’t use it. I can see some problem while ombi is loading, some 404 errors when loading js scripts (2.js for example). I think it’s a probelm with the rewrite engine, it doesn’t work as expected…
When the browser loads the script, it will retrieve it from the URL
https://my.domain.net/dist/2.js
that’s when error 404 occurs. But if I manually modify the query using the URL
https://my.domain.net/ombi/dist/2.js
the query returns a 200.
Extract from my ombi.conf:
<Location /ombi>
ProxyPass http://localhost:5000/ombi
ProxyPassReverse http://localhost:5000/ombi
Require all granted
</Location>
RewriteEngine on
RewriteRule ^/ombi$ https://MYURL/ombi/ [R=301,L]
RewriteCond %{HTTP_REFERER} "https://MYURL/ombi/"
RewriteCond %{REQUEST_URI} !^/ombi
RewriteRule ^(.*)$ /ombi [R=301,L]
Do you have any idea why the rewrite module doesn’t work?
Thx
I think it has been fixed. Someone edited the wiki with this commit message:
After using the previous apache config, it was not working because /dist/2.js was not loading. Someone from Discord suggested that the last rewrite line was incomplete and needed to be /ombi$1. This fixed my reverse proxy issue and it seems this should be how it should be for everyone.
@JMSolo - if you find time in your busy schedule, can you have a look this this one above - potential fix to this issue?
It has not been fixed. The edit fixed an issue probably unrelated to our problem.
Alright i got it working. Was quite annoying…
A copy of my ombi.conf (this is default) :
seedbox01:/etc/apache2/sites-enabled# cat ombi.conf
<Location /ombi>
ProxyPass http://localhost:5000/ombi
ProxyPassReverse http://localhost:5000/ombi
Require all granted
seedbox01:/etc/apache2/sites-enabled# pwd
/etc/apache2/sites-enabled
And then this was the big thing, even though it looks filled in, its not. You HAVE to manually type it “/ombi” :
I then simply restarted the ombi service from the dashboard and boom. Everything works.
Hope this helps all!
What version of Ombi is this?
The latest :
Unfortunately that’s not the real latest version, we’re all on that already. (JMSolo rolled back to this because it was the last stable version) After this version is where the rewrite engine stuff is needed, and that’s what we can’t figure out. I think the second to last rewritecond is wrong in the rev proxy examples page on ombi repo.
Ah, i wish it would have been posted here so id have known >_< oh well.
I have just released v3.0.3020 that no longer requires the rewrite rule.
That should help you guys!
