Closed LennyPenny closed 5 years ago
just tested here and working ok. Only thing I notice with your docker-compose is I would use full paths for the volumes.
Is there any way I can enable the enhanced logging via an environment variable or something? There must be a way to get some more detailed info as to whats going on
Does is still happen when hit jackett directly i.e not through a reverse proxy?
Bump - I have this issue as well.... not sure how to make the POST directly. Can try if someone can give me a curl command to throw at the container
Alright - my issue appears to be because the nginx reverse proxy I'm using is configuring:
proxy_set_header Connection "upgrade"
- ie https://github.com/dperson/nginx/blob/master/nginx.sh#L460-L461
and this isn't something Jackett can handle as per: https://github.com/Jackett/Jackett/issues/3712
I tested Jackett with a reverse proxy config leaving out the Connection config and we don't get a 400 when posting.
@LennyPenny see @scatat comment regarding reverse proxy configuration.
oki awesome, thank you all! Sadly I lost that setup but jackett is running greatly on my new one :+1:
Alright - my issue appears to be because the nginx reverse proxy I'm using is configuring:
proxy_set_header Connection "upgrade"
- ie dperson/nginx:nginx.sh@master
#L460-L461and this isn't something Jackett can handle as per: Jackett/Jackett#3712
I tested Jackett with a reverse proxy config leaving out the Connection config and we don't get a 400 when posting.
@scatat Hey! I'm hitting the exact issue you did with the nginx proxy. Can you explain how you resolved it exactly?
Every post request sent to jackett results in a 400 error with an empty response. I can't even turn on the enhanced logging as the post request to update the settings fails as well.
There are no logs after Jacketts successful start and loading of the indexers.
I also checked all file permissions, they are correctly being set to 1000 on the host.
Here's my docker-compose for it:
Some logs about the used versions:
Here's a screenshot of the failed request to enable enhanced logging:![https://vgy.me/JoVApx.png](https://vgy.me/JoVApx.png)
Do you have any idea what might be going wrong?