Problem with download links [solved]

Seafile Client
1

Hi all,

When i generate a download link with seafile client, my domain name appears two time in the link, as this : “https://mydomain/mydomain/f/b34a8eafa3/”.
Someone have an idea to solve it ?

Thank you for your help.

2

Is your service URL configured correctly?

3

Yes, URL are configured correctly in web interface and in configuration files, It’s why i don’t understand the problem.

4

Some redirect error in Nginx or Apache?

5

Yes, there is a redirect with apache, I have configure it as explained in Seafile server manual but i don’t use the standard https port, it can be the cause of the problem ?

6

Please post your apache config regarding Seafile and the part regarding URL From your Seafile config.

7

My apache config :

<IfModule mod_ssl.c>
    <VirtualHost *:8000>
            ServerName mydomain.com
            DocumentRoot /var/www
            Alias /media    /home/seafile/seafile-server-latest/seahub/media

            RewriteEngine On
            SSLEngine on

            SSLCertificateFile      /etc/letsencrypt/live/mydomain.com/fullchain.pem
            SSLCertificateKeyFile   /etc/letsencrypt/live/mydomain.com/privkey.pem

            <Location /media>
                    Require all granted
            </Location>

            #
            # seafile fileserver
            #
            ProxyPass /seafhttp http://127.0.0.1:8082
            ProxyPassReverse /seafhttp http://127.0.0.1:8082
            RewriteRule ^/seafhttp - [QSA,L]

            #
            # seahub
            #
            SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape
            SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
            ProxyPass / fcgi://127.0.0.1:8000/
    </virtualHost>

In ccnet.conf :
SERVICE_URL = https://mydomain.com:8000

In seahub_settings.py :
FILE_SERVER_ROOT = 'https://mydomain.com:8000/seafhttp'

8

You cannot use Port 8000 as it’s beeing used by seahub itself !
Change your port to e.g. 8080.

Did you not read the manual carefully enough ? :wink:

I am wondering that it works at all. :smiley:

9

Seahub is configured to use port 8000 in loopback interface, not in output interface.
And I can assure it work.

10

It may still cause problems, please change and test. If it doesn’t help you can change back.

11

If i change port I need to reconfigure some firewalls, there is no another way ?

12

You can stay with 8000, but I don’t know of anybody who has used 8000 for outgoing traffic in combination with apache or nginx. You could try on a machine locally first before you change any firewall settings.

13

I have try it with a local VM with the same seafile configuration and with another port to apache and i have the same problem.

14

Thank you for your help, I have finally find the problem.
It is just a little misconfiguration in web interface.

15

Can you post what was the error so we can learn?

16

It’s just a typing error in SERVICE_URL, I have write “https:///” instead of “https://”.

1 Like