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

space in folder or file name not working in web interface - Seafile Server 4.2.2 #1258

Closed
andi-blafasl opened this Issue Jun 1, 2015 · 34 comments

Comments

Projects
None yet
10 participants
@andi-blafasl

andi-blafasl commented Jun 1, 2015

I just upgraded my installation from 4.1.2 to 4.2.2 but now i cant access any files within a folder that contains a space in it's name or any files that contain space in their name!
I can access the file via sync-client browser and webdav. But if i try to open it in the web interface i get the error message "File no found". The error is also logged in the "seahub_django_request.log" file.

2015-06-01 22:10:11,970 [WARNING] django.request:144 get_response Not Found: /repo/b715329f-a70f-4146-ddff-364ccdc78837/raw/12_12_12%20asdf/mayr-wallpaper-02.jpg

@andi-blafasl andi-blafasl changed the title from space in folder name not working in web interface - Seafile Server 4.2.2 to space in folder or file name not working in web interface - Seafile Server 4.2.2 Jun 1, 2015

@freeplant

This comment has been minimized.

Show comment
Hide comment
@freeplant

freeplant Jun 1, 2015

Member

I can't reproduce the problem.

Member

freeplant commented Jun 1, 2015

I can't reproduce the problem.

@andi-blafasl

This comment has been minimized.

Show comment
Hide comment
@andi-blafasl

andi-blafasl Jun 2, 2015

I'm using Seafile behind Apache 2.4 installed on Ubuntu 14.04 with mod_proxy_fcgi.
@freeplant what's your setup you tested with?

andi-blafasl commented Jun 2, 2015

I'm using Seafile behind Apache 2.4 installed on Ubuntu 14.04 with mod_proxy_fcgi.
@freeplant what's your setup you tested with?

@andi-blafasl

This comment has been minimized.

Show comment
Hide comment
@andi-blafasl

andi-blafasl Jun 2, 2015

I have set up a test server without apache and this is working out of box.
The Problem must be related to my setup with Apache and mod_proxy_fcgi. But it worked with Seafile 4.1.2 without problems. Any changes related to file download?
I used the setup from Issues #884 and #1186 for my setup with Seafile 4.1.2

andi-blafasl commented Jun 2, 2015

I have set up a test server without apache and this is working out of box.
The Problem must be related to my setup with Apache and mod_proxy_fcgi. But it worked with Seafile 4.1.2 without problems. Any changes related to file download?
I used the setup from Issues #884 and #1186 for my setup with Seafile 4.1.2

@andi-blafasl

This comment has been minimized.

Show comment
Hide comment
@andi-blafasl

andi-blafasl Jun 2, 2015

Did another test with apache and mod_fastcgi with the setup described in the official server manual. Everything is working like a charm with this configuration.
The Problem is related to the configuration with mod_proxy_fcgi. I guess there is a problem with the "pathinfo" configuration and how the path is send from apache to the fastcgi appliaction.

Is there any chance to get seafile running with mod_proxy_fcgi instead of mod_fastcgi? I'm using PHP with mod_proxy_fcgi and don't want to load two different modules for the same thing ;-)

andi-blafasl commented Jun 2, 2015

Did another test with apache and mod_fastcgi with the setup described in the official server manual. Everything is working like a charm with this configuration.
The Problem is related to the configuration with mod_proxy_fcgi. I guess there is a problem with the "pathinfo" configuration and how the path is send from apache to the fastcgi appliaction.

Is there any chance to get seafile running with mod_proxy_fcgi instead of mod_fastcgi? I'm using PHP with mod_proxy_fcgi and don't want to load two different modules for the same thing ;-)

@tomrei

This comment has been minimized.

Show comment
Hide comment
@tomrei

tomrei Aug 19, 2015

it works for me with this apache configuration (apache 2.4 with mod_proxy_fcgi):

# Seafile file server
ProxyPass /seafhttp http://localhost:8082
ProxyPassReverse /seafhttp http://localhost:8082

# Seafile WebDAV server
ProxyPass /seafdav http://localhost:8080/seafdav
ProxyPassReverse /seafdav http://localhost:8080/seafdav

# Seafile seahub server
SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
ProxyPass / fcgi://localhost:8000/

That's the important line:

SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape

tomrei commented Aug 19, 2015

it works for me with this apache configuration (apache 2.4 with mod_proxy_fcgi):

# Seafile file server
ProxyPass /seafhttp http://localhost:8082
ProxyPassReverse /seafhttp http://localhost:8082

# Seafile WebDAV server
ProxyPass /seafdav http://localhost:8080/seafdav
ProxyPassReverse /seafdav http://localhost:8080/seafdav

# Seafile seahub server
SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
ProxyPass / fcgi://localhost:8000/

That's the important line:

SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape
@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 21, 2015

hi i have the same problem.
I'm using Seafile behind Apache 2.4.7 installed on Ubuntu 14.04 with mod_proxy_fcgi.
I'm using the same config as above from the two issues.
I tried it with changing the line

SetEnvIf Request_URI . proxy-fcgi-pathinfo=1

into

SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape

This doesn't work for me.

Some other ideas?

simplyRoba commented Aug 21, 2015

hi i have the same problem.
I'm using Seafile behind Apache 2.4.7 installed on Ubuntu 14.04 with mod_proxy_fcgi.
I'm using the same config as above from the two issues.
I tried it with changing the line

SetEnvIf Request_URI . proxy-fcgi-pathinfo=1

into

SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape

This doesn't work for me.

Some other ideas?

@tomrei

This comment has been minimized.

Show comment
Hide comment
@tomrei

tomrei Aug 21, 2015

Did you restart your apache?

tomrei commented Aug 21, 2015

Did you restart your apache?

@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 21, 2015

Yes of course ;)

It is the folder from the mobile app where the picures are strored automatically Camera Uploads.

The Django log shows this:

2015-08-20 17:04:53,259 [ERROR] django.request:210 handle_uncaught_exception Internal Server Error: /seafile/thumbnail/dea6d9ac-1d76-46cf-bbea-2a4b3f9f41ec/48/Camera%20Uploads/IMG_0532.JPG
Traceback (most recent call last):
  File "/home/seafile/seafile-pro-server-4.3.1/seahub/thirdpart/Django-1.5.12-py2.6.egg/django/core/handlers/base.py", line 113, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
  File "/home/seafile/seafile-pro-server-4.3.1/seahub/seahub/auth/decorators.py", line 26, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/home/seafile/seafile-pro-server-4.3.1/seahub/thirdpart/Django-1.5.12-py2.6.egg/django/views/decorators/http.py", line 147, in inner
    response = func(request, *args, **kwargs)
  File "/home/seafile/seafile-pro-server-4.3.1/seahub/seahub/thumbnail/views.py", line 101, in thumbnail_get
    thumbnail_file = os.path.join(THUMBNAIL_ROOT, str(size), obj_id)
  File "/usr/lib/python2.7/posixpath.py", line 75, in join
    if b.startswith('/'):
AttributeError: 'NoneType' object has no attribute 'startswith'

simplyRoba commented Aug 21, 2015

Yes of course ;)

It is the folder from the mobile app where the picures are strored automatically Camera Uploads.

The Django log shows this:

2015-08-20 17:04:53,259 [ERROR] django.request:210 handle_uncaught_exception Internal Server Error: /seafile/thumbnail/dea6d9ac-1d76-46cf-bbea-2a4b3f9f41ec/48/Camera%20Uploads/IMG_0532.JPG
Traceback (most recent call last):
  File "/home/seafile/seafile-pro-server-4.3.1/seahub/thirdpart/Django-1.5.12-py2.6.egg/django/core/handlers/base.py", line 113, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
  File "/home/seafile/seafile-pro-server-4.3.1/seahub/seahub/auth/decorators.py", line 26, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/home/seafile/seafile-pro-server-4.3.1/seahub/thirdpart/Django-1.5.12-py2.6.egg/django/views/decorators/http.py", line 147, in inner
    response = func(request, *args, **kwargs)
  File "/home/seafile/seafile-pro-server-4.3.1/seahub/seahub/thumbnail/views.py", line 101, in thumbnail_get
    thumbnail_file = os.path.join(THUMBNAIL_ROOT, str(size), obj_id)
  File "/usr/lib/python2.7/posixpath.py", line 75, in join
    if b.startswith('/'):
AttributeError: 'NoneType' object has no attribute 'startswith'
@tomrei

This comment has been minimized.

Show comment
Hide comment
@tomrei

tomrei Aug 21, 2015

try 'rm -rf /tmp/seahub_cache/*'

tomrei commented Aug 21, 2015

try 'rm -rf /tmp/seahub_cache/*'

@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 21, 2015

I restarted apache, seafile and seahub and cleared seahub cache and browser cache.

simplyRoba commented Aug 21, 2015

I restarted apache, seafile and seahub and cleared seahub cache and browser cache.

@tomrei

This comment has been minimized.

Show comment
Hide comment
@tomrei

tomrei Aug 21, 2015

Can you post your seahub_settings.py, ccnet.conf and seafile.conf

tomrei commented Aug 21, 2015

Can you post your seahub_settings.py, ccnet.conf and seafile.conf

@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 21, 2015

ccnet.conf:

[General]
USER_NAME = ******
ID = ******
NAME = ******
SERVICE_URL = https://my-domain.tld/seafile

[...]

seafile.conf:

Alias /media /home/seafile/seafile-server-latest/seahub/media
<Location /media>
    ProxyPass !
    Require all granted
</Location>

# seafile httpserver
ProxyPass /seafhttp http://127.0.0.1:8082
ProxyPassReverse /seafhttp http://127.0.0.1:8082

# Seafile WebDAV server
#ProxyPass /seafdav http://localhost:8080/seafdav
#ProxyPassReverse /seafdav http://localhost:8080/seafdav

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

seahub_settings.py:

[...]
FILE_SERVER_ROOT = 'https://my-domain.tld/seafhttp'

TIME_ZONE = 'Europe/Berlin'
LANGUAGE_CODE = 'de'
ENABLE_SIGNUP = False
SERVE_STATIC = False
SITE_BASE = 'https://my-domain.tld/seafile'
MEDIA_URL = '/media/'
SITE_ROOT = '/seafile/'
COMPRESS_URL = MEDIA_URL
STATIC_URL = MEDIA_URL + 'assets/'
[...]

simplyRoba commented Aug 21, 2015

ccnet.conf:

[General]
USER_NAME = ******
ID = ******
NAME = ******
SERVICE_URL = https://my-domain.tld/seafile

[...]

seafile.conf:

Alias /media /home/seafile/seafile-server-latest/seahub/media
<Location /media>
    ProxyPass !
    Require all granted
</Location>

# seafile httpserver
ProxyPass /seafhttp http://127.0.0.1:8082
ProxyPassReverse /seafhttp http://127.0.0.1:8082

# Seafile WebDAV server
#ProxyPass /seafdav http://localhost:8080/seafdav
#ProxyPassReverse /seafdav http://localhost:8080/seafdav

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

seahub_settings.py:

[...]
FILE_SERVER_ROOT = 'https://my-domain.tld/seafhttp'

TIME_ZONE = 'Europe/Berlin'
LANGUAGE_CODE = 'de'
ENABLE_SIGNUP = False
SERVE_STATIC = False
SITE_BASE = 'https://my-domain.tld/seafile'
MEDIA_URL = '/media/'
SITE_ROOT = '/seafile/'
COMPRESS_URL = MEDIA_URL
STATIC_URL = MEDIA_URL + 'assets/'
[...]
@tomrei

This comment has been minimized.

Show comment
Hide comment
@tomrei

tomrei Aug 21, 2015

I don't notice a difference between your and my configuration, which could be responsible for this.
But I'm using a subdomain for seafile. Maybe try this way?

tomrei commented Aug 21, 2015

I don't notice a difference between your and my configuration, which could be responsible for this.
But I'm using a subdomain for seafile. Maybe try this way?

@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 21, 2015

Are you using SSL?

I tried it but i could find the right config can you show me your seafile.conf?

simplyRoba commented Aug 21, 2015

Are you using SSL?

I tried it but i could find the right config can you show me your seafile.conf?

@tomrei

This comment has been minimized.

Show comment
Hide comment
@tomrei

tomrei Aug 21, 2015

yes, I use SSL.
my apache seafile config:

<VirtualHost *:443>
                ServerName seafile.example.com
                DocumentRoot /var/www
                Alias /media /home/seafile/seafile-server-latest/seahub/media

                RewriteEngine On

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

                # Seafile file server
                ProxyPass /seafhttp http://localhost:8082
                ProxyPassReverse /seafhttp http://localhost:8082

                # Seafile WebDAV server
                ProxyPass /seafdav http://localhost:8080/seafdav
                ProxyPassReverse /seafdav http://localhost:8080/seafdav

                # Seafile seahub server
                SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape
                SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
                ProxyPass / fcgi://localhost:8000/

                SSLEngine on
                SSLCertificateFile      /etc/ssl/apache2/seafile/seafile.crt
                SSLCertificateKeyFile   /etc/ssl/apache2/seafile/seafile.key
                SSLCertificateChainFile /etc/ssl/apache2/seafile/sub.class1.server.sha2.ca.pem
                SSLCACertificateFile    /etc/ssl/apache2/seafile/ca-sha2.pem


                SSLProtocol All -SSLv2 -SSLv3
                SSLCompression off
                SSLHonorCipherOrder On
                SSLCipherSuite ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK
                Header add Strict-Transport-Security "max-age=15768000"

</VirtualHost>

my seahub_settings.py:

[...]
FILE_SERVER_ROOT = 'https://seafile.example.com/seafhttp'
TIME_ZONE = 'Europe/Berlin'
LOGIN_ATTEMPT_LIMIT = 3
FILE_PREVIEW_MAX_SIZE = 100 * 1024 * 1024
[...]

ccnet.conf:

[...]
SERVICE_URL = https://seafile.example.com
[...]

I hope it helps :)

tomrei commented Aug 21, 2015

yes, I use SSL.
my apache seafile config:

<VirtualHost *:443>
                ServerName seafile.example.com
                DocumentRoot /var/www
                Alias /media /home/seafile/seafile-server-latest/seahub/media

                RewriteEngine On

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

                # Seafile file server
                ProxyPass /seafhttp http://localhost:8082
                ProxyPassReverse /seafhttp http://localhost:8082

                # Seafile WebDAV server
                ProxyPass /seafdav http://localhost:8080/seafdav
                ProxyPassReverse /seafdav http://localhost:8080/seafdav

                # Seafile seahub server
                SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape
                SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
                ProxyPass / fcgi://localhost:8000/

                SSLEngine on
                SSLCertificateFile      /etc/ssl/apache2/seafile/seafile.crt
                SSLCertificateKeyFile   /etc/ssl/apache2/seafile/seafile.key
                SSLCertificateChainFile /etc/ssl/apache2/seafile/sub.class1.server.sha2.ca.pem
                SSLCACertificateFile    /etc/ssl/apache2/seafile/ca-sha2.pem


                SSLProtocol All -SSLv2 -SSLv3
                SSLCompression off
                SSLHonorCipherOrder On
                SSLCipherSuite ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK
                Header add Strict-Transport-Security "max-age=15768000"

</VirtualHost>

my seahub_settings.py:

[...]
FILE_SERVER_ROOT = 'https://seafile.example.com/seafhttp'
TIME_ZONE = 'Europe/Berlin'
LOGIN_ATTEMPT_LIMIT = 3
FILE_PREVIEW_MAX_SIZE = 100 * 1024 * 1024
[...]

ccnet.conf:

[...]
SERVICE_URL = https://seafile.example.com
[...]

I hope it helps :)

@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 21, 2015

Thanks for your config i can acces seahub now throw the subdomain but the problem is still their.
Because i have no valid SSL for the subdamoin i tried it on the root and still the same problem.

I cleared seahub and browser cache. And restarted everything ^^

simplyRoba commented Aug 21, 2015

Thanks for your config i can acces seahub now throw the subdomain but the problem is still their.
Because i have no valid SSL for the subdamoin i tried it on the root and still the same problem.

I cleared seahub and browser cache. And restarted everything ^^

@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 21, 2015

Do you have something else in the seahub_settings.py aside from this:

SECRET_KEY = *****

FILE_SERVER_ROOT = 'https://my-domain.tld/seafhttp'

TIME_ZONE = 'Europe/Berlin'
LANGUAGE_CODE = 'de'
ENABLE_SIGNUP = False

EMAIL_USE_TLS = False
EMAIL_HOST = *****
EMAIL_HOST_USER = *****
EMAIL_HOST_PASSWORD = *****
EMAIL_PORT = '25'
DEFAULT_FROM_EMAIL = EMAIL_HOST_USER
SERVER_EMAIL = EMAIL_HOST_USER

DATABASES = {
    [...]
}

simplyRoba commented Aug 21, 2015

Do you have something else in the seahub_settings.py aside from this:

SECRET_KEY = *****

FILE_SERVER_ROOT = 'https://my-domain.tld/seafhttp'

TIME_ZONE = 'Europe/Berlin'
LANGUAGE_CODE = 'de'
ENABLE_SIGNUP = False

EMAIL_USE_TLS = False
EMAIL_HOST = *****
EMAIL_HOST_USER = *****
EMAIL_HOST_PASSWORD = *****
EMAIL_PORT = '25'
DEFAULT_FROM_EMAIL = EMAIL_HOST_USER
SERVER_EMAIL = EMAIL_HOST_USER

DATABASES = {
    [...]
}
@tomrei

This comment has been minimized.

Show comment
Hide comment
@tomrei

tomrei Aug 21, 2015

Is the error in the Django log still the same?
Take a look into the apache error log. Maybe there's something suspicious.
Belongs everything in /home/seafile the seafile user? -> chown -R seafile:seafile /home/seafile
My seahub_settings.py is as three posts above plus SECRET_KEY and DATABASES.

tomrei commented Aug 21, 2015

Is the error in the Django log still the same?
Take a look into the apache error log. Maybe there's something suspicious.
Belongs everything in /home/seafile the seafile user? -> chown -R seafile:seafile /home/seafile
My seahub_settings.py is as three posts above plus SECRET_KEY and DATABASES.

@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 21, 2015

Django lo shows still same message like 20.000 times ;)
The apache error log is empty.
Yes everything belongs to the seafile user but to be sure i executed the command.

OK then it was right to remove all this:

SERVE_STATIC = False
MEDIA_URL = '/seafmedia/'
SITE_ROOT = '/seafile/'
COMPRESS_URL = MEDIA_URL
STATIC_URL = MEDIA_URL + 'assets/'

simplyRoba commented Aug 21, 2015

Django lo shows still same message like 20.000 times ;)
The apache error log is empty.
Yes everything belongs to the seafile user but to be sure i executed the command.

OK then it was right to remove all this:

SERVE_STATIC = False
MEDIA_URL = '/seafmedia/'
SITE_ROOT = '/seafile/'
COMPRESS_URL = MEDIA_URL
STATIC_URL = MEDIA_URL + 'assets/'
@tomrei

This comment has been minimized.

Show comment
Hide comment
@tomrei

tomrei Aug 21, 2015

Is it running on your root domain now?
Can you describe again, what's not working.
My problem was, I couldn't preview any file (with a special character) on the webinterface.
Besides that everything was working very well.

tomrei commented Aug 21, 2015

Is it running on your root domain now?
Can you describe again, what's not working.
My problem was, I couldn't preview any file (with a special character) on the webinterface.
Besides that everything was working very well.

@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 22, 2015

Yeah it runs now on the root domain.
The problem is simple when their is a space in the folder or file name like here in Camera Uploads
image
The Thumbainls are not working like you see in the screenshot. And i can´t access the file over the webinterface. When its an image it says The image could not be loaded and on the other files just The file doesn´t exist.

When i just rename the folder and remove the space like here:
image
Thumbnails working and i can access the files normaly. I do not even have to restart anything this works instantly.

The same for files with a space in its name. They just can´t be accessed over the webinterface. Sync is working fine. So files aren´t broken or anything.

I'am using Seafile 4.3.1 Apache 2.4.7

simplyRoba commented Aug 22, 2015

Yeah it runs now on the root domain.
The problem is simple when their is a space in the folder or file name like here in Camera Uploads
image
The Thumbainls are not working like you see in the screenshot. And i can´t access the file over the webinterface. When its an image it says The image could not be loaded and on the other files just The file doesn´t exist.

When i just rename the folder and remove the space like here:
image
Thumbnails working and i can access the files normaly. I do not even have to restart anything this works instantly.

The same for files with a space in its name. They just can´t be accessed over the webinterface. Sync is working fine. So files aren´t broken or anything.

I'am using Seafile 4.3.1 Apache 2.4.7

@tomrei

This comment has been minimized.

Show comment
Hide comment
@tomrei

tomrei Aug 22, 2015

Okay, it's the same problem. (Spaces aren't the only characters affected, also öüä etc.)
I'am using Seafile 4.3.1, Apache 2.4.16 (<- maybe they did a fix for the proxy passes)
Do you use ./seahub.sh start-fastcgi?
I'm run out of ideas at this point.

tomrei commented Aug 22, 2015

Okay, it's the same problem. (Spaces aren't the only characters affected, also öüä etc.)
I'am using Seafile 4.3.1, Apache 2.4.16 (<- maybe they did a fix for the proxy passes)
Do you use ./seahub.sh start-fastcgi?
I'm run out of ideas at this point.

@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 22, 2015

I'am using the startscript as given in the manual. And the use fastcgi thing is set to true.
Then this seems to be an apache bug not a seafile bug. Which OS and Version are you running on your server?

simplyRoba commented Aug 22, 2015

I'am using the startscript as given in the manual. And the use fastcgi thing is set to true.
Then this seems to be an apache bug not a seafile bug. Which OS and Version are you running on your server?

@tomrei

This comment has been minimized.

Show comment
Hide comment
@tomrei

tomrei Aug 22, 2015

I run gentoo linux, which is a rolling release.
Just wait a few days. I hope, somebody will answer with a solution for you.

tomrei commented Aug 22, 2015

I run gentoo linux, which is a rolling release.
Just wait a few days. I hope, somebody will answer with a solution for you.

@simplyRoba

This comment has been minimized.

Show comment
Hide comment
@simplyRoba

simplyRoba Aug 22, 2015

Yeah ill wait a bit and maybe post an issue on the seahub repo.
Anyway thank you for your help 😄

simplyRoba commented Aug 22, 2015

Yeah ill wait a bit and maybe post an issue on the seahub repo.
Anyway thank you for your help 😄

@yopbot

This comment has been minimized.

Show comment
Hide comment
@yopbot

yopbot Dec 10, 2015

Same problem here, with seafile server 5.0.2 on centos 7 and fastcgi, I can't preview nor download the files with spaces in the name.

yopbot commented Dec 10, 2015

Same problem here, with seafile server 5.0.2 on centos 7 and fastcgi, I can't preview nor download the files with spaces in the name.

@shoeper

This comment has been minimized.

Show comment
Hide comment
@shoeper

shoeper Feb 9, 2016

Collaborator

Spaces in folder or file names does work as long as the webserver passes the path properly.

Collaborator

shoeper commented Feb 9, 2016

Spaces in folder or file names does work as long as the webserver passes the path properly.

@dave-fl

This comment has been minimized.

Show comment
Hide comment
@dave-fl

dave-fl Feb 25, 2016

This is broken with Ubuntu 14.04 LTS. It works just fine without Apache. But does not work with Apache. Does anyone have instructions to make this work with Apache?

dave-fl commented Feb 25, 2016

This is broken with Ubuntu 14.04 LTS. It works just fine without Apache. But does not work with Apache. Does anyone have instructions to make this work with Apache?

@shoeper

This comment has been minimized.

Show comment
Hide comment
@shoeper

shoeper Feb 25, 2016

Collaborator

read the issue linked above.

Collaborator

shoeper commented Feb 25, 2016

read the issue linked above.

@dave-fl

This comment has been minimized.

Show comment
Hide comment
@dave-fl

dave-fl Feb 25, 2016

Sorry I missed that. I tested with fast cgi instead of mod_proxy_fcgi and I can confirm that the system now works with spaces. The install instructions should be updated so that mod_proxy_fcgi is not used or at least add a note that there is a known issue.

It seems the bug is in apache 2.4.7 and was fixed in 2.4.10 which isn't available for ubuntu 14.04.

dave-fl commented Feb 25, 2016

Sorry I missed that. I tested with fast cgi instead of mod_proxy_fcgi and I can confirm that the system now works with spaces. The install instructions should be updated so that mod_proxy_fcgi is not used or at least add a note that there is a known issue.

It seems the bug is in apache 2.4.7 and was fixed in 2.4.10 which isn't available for ubuntu 14.04.

@andi-blafasl

This comment has been minimized.

Show comment
Hide comment
@andi-blafasl

andi-blafasl Feb 26, 2016

I'm also using seafile on ubuntu 14.04 with mod_proxy_fcgi.
Because of the improofments in newer apache versions I'm using the PPA from Ondrej https://launchpad.net/~ondrej/+archive/ubuntu/apache2 which has Apache 2.4.18 for ubuntu 14.04.
Running with PHP-FPM and using mod_proxy_fcgi it is a rock solid solution for me.

andi-blafasl commented Feb 26, 2016

I'm also using seafile on ubuntu 14.04 with mod_proxy_fcgi.
Because of the improofments in newer apache versions I'm using the PPA from Ondrej https://launchpad.net/~ondrej/+archive/ubuntu/apache2 which has Apache 2.4.18 for ubuntu 14.04.
Running with PHP-FPM and using mod_proxy_fcgi it is a rock solid solution for me.

@dave-fl

This comment has been minimized.

Show comment
Hide comment
@dave-fl

dave-fl Feb 26, 2016

Yes I was able to test with the PPA afterwards as well and confirm that it works. I am up and running. The only thing that I could not get to work was webdav with fcgi. It works fine without fcgi and regular proxy.

dave-fl commented Feb 26, 2016

Yes I was able to test with the PPA afterwards as well and confirm that it works. I am up and running. The only thing that I could not get to work was webdav with fcgi. It works fine without fcgi and regular proxy.

@dbeuchler

This comment has been minimized.

Show comment
Hide comment
@dbeuchler

dbeuchler Mar 9, 2016

I reinstalled my root server to use debian 8.3 with Apache 2.4.10 and hoped that the bug was fixed there. No change.

2.4.18 is not possible for me because I have some other dependencies.

Can anyone confirm that it works with 2.4.10?

dbeuchler commented Mar 9, 2016

I reinstalled my root server to use debian 8.3 with Apache 2.4.10 and hoped that the bug was fixed there. No change.

2.4.18 is not possible for me because I have some other dependencies.

Can anyone confirm that it works with 2.4.10?

@evdbovenkamp

This comment has been minimized.

Show comment
Hide comment
@evdbovenkamp

evdbovenkamp Aug 17, 2017

I spent a lot of time to solve this problem and there is an easy solution; If this problem happens when you have Ubuntu 14.0x install, do a upgrade to the latest version with the command; do-release-upgrade
The problem is the Apache version. This solves the problem, because with the new Ubuntu version, also a new version of Apache will be installed.

evdbovenkamp commented Aug 17, 2017

I spent a lot of time to solve this problem and there is an easy solution; If this problem happens when you have Ubuntu 14.0x install, do a upgrade to the latest version with the command; do-release-upgrade
The problem is the Apache version. This solves the problem, because with the new Ubuntu version, also a new version of Apache will be installed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment