search

haiwen / seafile-iOS

iOS client for seafile
Apache License 2.0
221 stars 150 forks source link

Waiting for upload... #8

Closed dseichter closed 10 years ago

dseichter commented 11 years ago

Using the seafilePro App 1.0 on my iPad2 and iPhone5. Everything works fine but I can't upload any file. If I add a photo, an attachment, whatever, the file is listed inside the choosen library, but the status is "Waiting for upload..."

I restartet everything, App, iPhone/iPad, re-added the account, restarted the server, but nothing. The status is still the same "Waiting for upload...".

freeplant commented 11 years ago

Sorry, I can't reproduce your problem. Can your try upload file to seacloud.cc?

dseichter commented 11 years ago

Hello,

I will create an account today in the evening and try again. I will report you as soon as I have done it.

Daniel

Am 02.09.2013 14:43, schrieb plt:

Sorry, I can't reproduce your problem. Can your try upload file to seacloud.cc?

— Reply to this email directly or view it on GitHub https://github.com/haiwen/seafile-iOS/issues/8#issuecomment-23658000.

dseichter commented 11 years ago

Hello,

so, now I have some logfiles: _seahub_djanigrequest.log: 2013-09-03 04:39:37,248 [WARNING] django.request:146 get_response Not Found: /upload-api/8865d2e6 2013-09-03 04:39:37,248 [WARNING] django.request:141 process_view Forbidden (Referer checking failed - no Referer.): /upload-api/8865d2e6

access.log of apache: 93.205.3.223 - - [02/Sep/2013:22:44:44 +0200] "GET /api2/starredfiles/ HTTP/1.1" 200 2 "-" "SeafilePro/1.0 CFNetwork/609.1.4 Darwin/13.0.0" 93.205.3.223 - - [02/Sep/2013:22:44:44 +0200] "GET /api2/repos/ HTTP/1.1" 200 4570 "-" "SeafilePro/1.0 CFNetwork/609.1.4 Darwin/13.0.0" 93.205.3.223 - - [02/Sep/2013:22:44:47 +0200] "GET /api2/repos/746bc0ec-64ca-48a6-9a7d-c095f9194f97/dir/?p=/&oid=829bf421bc487ece4cf1f7d93cc0b60427fdd2d8 HTTP/1.1" 200 10 "-" "SeafilePro/1.0 CFNetwork/609.1.4 Darwin/13.0.0" 93.205.3.223 - - [02/Sep/2013:22:44:47 +0200] "GET /api2/repos/746bc0ec-64ca-48a6-9a7d-c095f9194f97/upload-link/ HTTP/1.1" 200 52 "-" "SeafilePro/1.0 CFNetwork/609.1.4 Darwin/13.0.0" 93.205.3.223 - - [02/Sep/2013:22:44:48 +0200] "POST /upload-api/8865d2e6 HTTP/1.1" 404 10369 "-" "SeafilePro/1.0 (iPhone; iOS 6.1.4; Scale/2.00)"

Is it a problem of the iOS client or a problem on my server?

Thank you, Daniel

Am 02.09.2013 14:43, schrieb plt:

Sorry, I can't reproduce your problem. Can your try upload file to seacloud.cc?

— Reply to this email directly or view it on GitHub https://github.com/haiwen/seafile-iOS/issues/8#issuecomment-23658000.

dseichter commented 11 years ago

Additional Info: I am using the version 1.8.3 of the seafile server.

Am 02.09.2013 14:43, schrieb plt:

Sorry, I can't reproduce your problem. Can your try upload file to seacloud.cc?

— Reply to this email directly or view it on GitHub https://github.com/haiwen/seafile-iOS/issues/8#issuecomment-23658000.

dseichter commented 11 years ago

Hello,

Just tested with seafile.cc account and everything works fine. My server is set up using apache and https. The error logs I sent you yesterday are the same. Do I have to set up anything in my config for apache or seafile? The Windows client and webfrontend works fine.

Since I have more than three files waiting for upload inside the library, the iOS app will be killed after some seconds.

I also reinstalled the iOS app, but no changes, same problems :(

Thank you, Daniel

Am 02.09.2013 um 14:43 schrieb plt notifications@github.com:

Sorry, I can't reproduce your problem. Can your try upload file to seacloud.cc?

— Reply to this email directly or view it on GitHub.

freeplant commented 11 years ago

You may configure HTTPS in an old way, which is not consistent with server version 1.8. Please re-config HTTPS using our recommend way as in https://github.com/haiwen/seafile/wiki/Deploy-Seafile-with-apache and https://github.com/haiwen/seafile/wiki/Enable-Https-on-Seafile-web-with-Apache

freeplant commented 11 years ago

If you still have the problem, you can post your config files. I will check what is wrong.

dseichter commented 11 years ago

Hello,

it works now!

I checked all my configuration files and found one missing configuration -> missing ProxyHttp

I thought, you either have to use FastCGI or have to use ProxyHttp, but not both at the same time. I added the missing configuration of ProxyHttp, restarted the seafile and apache and now, everything works fine, without any errors.

Thank you very much.

Daniel

Am 04.09.2013 04:45, schrieb plt:

If you still have the problem, you can post your config files. I will check what is wrong.

— Reply to this email directly or view it on GitHub https://github.com/haiwen/seafile-iOS/issues/8#issuecomment-23762487.

ghost commented 10 years ago

Hello Daniel

I have the same problem like you had, but I don't understand your solution. What do you mean with you added the missing configuration of ProxyHttp? And how did you find out that there was a missing configuration file? I think I used the apache2-mod proxy_http as it is described in the article about how to enable https on Seafile web with apache, so I don't know why the iPhone and iPad clients are having this "Waiting for upload" problem.

dseichter commented 10 years ago

Hello Clemens,

I will sent you tomorrow my config of apache (today I am not able to connect to my server).

Daniel

Von meinem iPhone gesendet

Am 30.12.2013 um 23:46 schrieb clemensfiechter notifications@github.com:

Hello Daniel

I have the same problem like you had, but I don't understand your solution. What do you mean with you added the missing configuration of ProxyHttp? And how did you find out that there was a missing configuration file? I think I used the apache2-mod proxy_http as it is described in the article about how to enable https on Seafile web with apache, so I don't know why the iPhone and iPad clients are having this "Waiting for upload" problem.

— Reply to this email directly or view it on GitHub.

dseichter commented 10 years ago

Hello,

I now just had the posibility to connect to my server:

In my config-file of apache, I had the following for seafile (but I migrated to nginx two weeks ago). You do not need to use port 11666 g:

seafile

Listen 11666 FastCGIExternalServer /var/www/seahub.fcgi -host 127.0.0.1:8000

VirtualHost for seafile on Port 11666

<VirtualHost *:11666> ServerName www.dseichter.de DocumentRoot /var/www Alias /media /opt/seafile/seafile-server-2.0.3/seahub/media

activate Rewrite

RewriteEngine On

#

seafile httpserver

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

#

seahub

# RewriteRule ^/(media._)$ /$1 [QSA,L,PT] RewriteCond %{REQUESTFILENAME} !-f RewriteRule ^(.)$ /seahub.fcgi$1 [QSA,L,E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

SSLEngine On SSLCertificateFile /etc/pki/tls/certs/www.dseichter.de.crt SSLCertificateKeyFile /etc/pki/tls/private/www.dseichter.de.key SSLCertificateChainFile /etc/pki/tls/certs/www.dseichter.de.ca SSLProtocol -ALL +SSLv3 +TLSv1 SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:!LOW:!SSLv2:!EXPORT

ErrorLog /var/log/httpd/dseichter.de_seafile_error.log CustomLog /var/log/httpd/dseichter.de_seafile_access.log combined

In my seahub_settings.py I had HTTP_SERVER_ROOT = "https://www.dseichter.de:11666/seafhttp" SECRET_KEY = "XXXXXXXXXXXX" SERVE_STATIC = False MEDIA_URL = '/media/' SITE_ROOT = '/'

With that configuration, I got everything to work.

Daniel

Am 30.12.2013 23:46, schrieb clemensfiechter:

Hello Daniel

I have the same problem like you had, but I don't understand your solution. What do you mean with you added the missing configuration of ProxyHttp? And how did you find out that there was a missing configuration file? I think I used the apache2-mod proxy_http as it is described in the article about how to enable https on Seafile web with apache, so I don't know why the iPhone and iPad clients are having this "Waiting for upload" problem.

— Reply to this email directly or view it on GitHub https://github.com/haiwen/seafile-iOS/issues/8#issuecomment-31373883.

ghost commented 10 years ago

thanks for your help, but i found out why it didn't work for me. Actually it's a very silly mistake, in my ccnet.conf, i did change the http to https, but i forgot to change the hostname itself.. :) now i changed that and it works. Thank you anyway for sending me your configuration files.

ghost commented 10 years ago

Hi, I have the same problem. Can I solve it without changing some seafile configuration? Im not using https. Thanks [EDIT] I could imaging that its a dead lock happening, since im trying to upload quite a number of files..

jsongo commented 6 years ago

Unfortunately the same problem too, while sometimes it works fine but sometimes doesn't. It may be an occasionally-happened problem that your team should take serious of.

scottcc commented 6 years ago

Hey @jsongo, that comment is from 2014 (and is a deleted user), and this ticket is closed. You should probably open a new ticket and link against this rather than commenting 4 years after the fact. That's just a suggestion I have, I'm not affiliated with haiwen in any way (just an avid user of the software). Cheers!