-
Notifications
You must be signed in to change notification settings - Fork 25
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
Proxy Config #72
Comments
You might need to look at What are the errors you see? |
@pannal, while waiting for your help, I've been tinkering a bit. This will work with regular http but not https.
|
Ok, more progress. It seems that Kitana is specifying http:// in several places where it's not needed. If that was left out, it would work fine. The browser sees the page loaded as https then the html is asking for http so by default, it won't mix http and https on the same page. That's the remaining issue. |
in base.jinja2 line 16 In the index.jinja2 you have Again, because it's not properly putting in https it causes issues. It really doesn't need anything before /kitana. I can't find where in the code you do that so I can try altering the code to fix the issue. I'm a novice with python. |
I told you exactly what you might need to look at in my first reply. Try setting proxy base (the first parameter I hinted at) to https://yourdomain (without slash at the end, without /kitana - see README). |
Also, you might need to add a rewrite for the statics, as per sample conf: https://github.com/pannal/Kitana/blob/master/deployment/nginx/sample.conf |
Putting in the host made it work. I wonder what's so different with your engine than all the other typical *arr apps where the simple apache location and adding /kitana is enough. Not my place to challenge. :-) Hitting restart plugin on SubZero results in this:
|
That's this issue: pannal/Sub-Zero.bundle#753 |
That's an issue I can't solve - routing. Wherever/whatever runs Kitana can't reach that host. |
It's all on the same host. Any ideas how to resolve that? |
No idea. You can select a different "connection type" to connect to your Plex, though. Through the server selection screen in Kitana (click your server name). Use something local. |
Trying to get kitana to run through an apache proxy so I can access it via https://mydomain.tld/kitana. I'm sure I have the apache config right but what are the correct flags for the service file?
Currently I'm trying this with no success:
ExecStart=/usr/bin/python3 /opt/Kitana/kitana.py --behind-proxy=true --prefix=/kitana
The text was updated successfully, but these errors were encountered: