You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Ombi base setting URL does not work. Setting will show as saved in GUI, but URL does not include the base url. And when you add the base url to the ingress path, Ombi is no longer reachable.
To Reproduce
Steps to reproduce the behavior:
After setting up ombi for the first time, add base url in gui settings and save.
Edit truechart configuration to use cluster ip, and configure ingress path to /baseurl and Prefix.
After Ombi redeploys try going to sub.domain/baseurl and ombi will not be reachable anymore.
Expected behavior
The base url to be applied and to be able to reach ombi via sub.domain/baseurl with using traefik ingress.
Additional context
I reached out to Ombi Support and they suggested adding the startup command --base-url to ombi. They also mention the linuxserver.io's ombi docker image includes this feature via and ENV variable.
The text was updated successfully, but these errors were encountered:
I reached out to Ombi Support and they suggested adding the startup command --base-url to omb
If they offer a GUI option (like you said) that should just work.
They also mention the linuxserver.io's ombi docker image includes this feature via and ENV variable.
Yes and we do not, because not every container creator is going to cover for their fuckups. (and lsio is not really very well compatible with kubernetes permissions)
In short:
I'm comming to understand why k8s-at-home stopped building ombi containers and supporting ombi, there are alternatives and it seems the Ombi devs don't really care fixing their own issues.
That being said:
Closed as adding args to the GUI has been made part of #842 right after adding this issue.
Describe the bug
Ombi base setting URL does not work. Setting will show as saved in GUI, but URL does not include the base url. And when you add the base url to the ingress path, Ombi is no longer reachable.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The base url to be applied and to be able to reach ombi via sub.domain/baseurl with using traefik ingress.
Additional context
I reached out to Ombi Support and they suggested adding the startup command --base-url to ombi. They also mention the linuxserver.io's ombi docker image includes this feature via and ENV variable.
The text was updated successfully, but these errors were encountered: