Cannot access transmission interface

,

Hello,
following a power outage at my home, I had some data corrupted on my Yunohost.
This lead me to remove and reinstall transmission.
So I uninstall it, run a apt remove transmission-* to be sure to get ride of all the data and reinstalled it.
Transmission is running, the daemon works correctly and I can see in the log that it retrieve the torrent correctly, however I cannot access to the interface:
When I click on the transmission button in the user panel, the page just “refresh”.

In firefox debugger, I have these messages:

GET https://mydomain.tld/torrent 
[HTTP/2.0 301 Moved Permanently 0ms]
GET https://mydomain.tld/torrent/ 
[HTTP/2.0 301 Moved Permanently 0ms]
GET https://mydomain.tld/torrent/transmission/web/ 
[HTTP/2.0 301 Moved Permanently 0ms]
GET https://mydomain.tld/transmission/web/ 
[HTTP/2.0 302 Found 145ms]
GET https://mydomain.tld/yunohost/sso/
[HTTP/2.0 200 OK 265ms]

I don’t find anything useful in nginx log files or any other ones.
I tried nevertheless to restart nginx & transmission-daemon but to no avail.
An idea on how to solve this issue?

Bonjour,
On dirait qu’il y a un problème avec le slash final :

GET https://mydomain.tld/torrent 
[HTTP/2.0 301 Moved Permanently 0ms]
GET https://mydomain.tld/torrent/ 

Je ne connais pas bien transmission, mais ça ressemble à

  • un paramètre nginx (slash, pas de slash)
  • une URL rewriting qui aurait mal tournée.

Je pense que le slash à la fin est responsable, mais je ne suis pas sûr que cela t’aide beaucoup !

Hello,
It looks like there is a problem with the final slash:

GET https: //mydomain.tld/torrent
[HTTP / 2.0 301 Moved Permanently 0ms]
GET https: //mydomain.tld/torrent/

I do not know transmission well, but it looks like

a nginx parameter (slash, no slash)
a rewriting URL that would have gone wrong.

I think the slash at the end is responsible, but I’m not sure it helps you a lot!

Et bien, j’ai tenté de bidouiller les paramètres de nginx, mais pas mieux…
Voici le fichier de config (100% standard de l’installation):

location /torrent/transmission {
    proxy_pass http://127.0.0.1:9091/torrent/transmission;

    # Include SSOWAT user panel.
    include conf.d/yunohost_panel.conf.inc;
    more_clear_input_headers 'Accept-Encoding';
}

location /torrent/ {
    proxy_pass http://127.0.0.1:9091/;
}

location /torrent/downloads {
    alias /home/yunohost.transmission/completed/;
    autoindex on;
    autoindex_exact_size off;

    # Include SSOWAT user panel.
    include conf.d/yunohost_panel.conf.inc;
    more_clear_input_headers 'Accept-Encoding';
}

Les logs de /var/log/nginx/mydomain.tld-access.log, mais rien de vraiment intéressant:

2a01:e34:ee16:5630:3dfa:b1a1:bf82:874b - - [04/May/2019:18:56:27 +0200] "GET /transmission/web/ HTTP/2.0" 302 549 "https://mydomain.tld/yunohost/sso/" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0"
2a01:e34:ee16:5630:3dfa:b1a1:bf82:874b - nicolas [04/May/2019:18:56:27 +0200] "GET /yunohost/sso/ HTTP/2.0" 200 4619 "https://mydomain.tld/yunohost/sso/" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0"

Une idée?

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.