Cant log in with Android Client

[Александар Васиљевић]

HI,

I cant log in with android client. I get no error. 

Log in button just grays out.

win client works well, and web interface works without problems. 

I have reinstalled the app and the seafile version is 3.0.2.

If you have no solution could you tell me the way how to debug this. What to look for?

Thank you very much.

Best regards

[Shuai Lin]

Is the server address you type correct? By default you need to include the port in the server url, like http://www.myseafile.com:8000

--
You received this message because you are subscribed to the Google Groups "seafile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to seafile+u...@googlegroups.com.
To post to this group, send email to sea...@googlegroups.com.
Visit this group at http://groups.google.com/group/seafile.
For more options, visit https://groups.google.com/d/optout.

[Александар Васиљевић]

Server is configured with Apache proxy and fastcgi. It should connect with the domain on port 80. I checked apache logs it just gives me, after some time, 408 error Request timed out.

[Александар Васиљевић]

Hello,

I thought that mobile client connects the same way web browser does. But in this case web browser works without problems and mobile client gets request timeout. Could you tell me what settings to look for, in what way is the connection of mobile client different to the connection of the web browser?

Thanks

[Shuai Lin]

Can you post the apache logs when you tried to log in from your phone?

--

[Александар Васиљевић]

212.200.65.133 is the ip adress of android phone. First entries are from the phone web browser. The last two entries are from the android app.

Thanks

212.200.65.133 - - [11/Jun/2014:07:21:55 +0100] "GET / HTTP/1.1" 301 233

212.200.65.133 - - [11/Jun/2014:07:22:00 +0100] "GET / HTTP/1.1" 302 -

212.200.65.133 - - [11/Jun/2014:07:22:01 +0100] "GET /accounts/login HTTP/1.1" 301 -

212.200.65.133 - - [11/Jun/2014:07:22:02 +0100] "GET /accounts/login/ HTTP/1.1" 200 11529

212.200.65.133 - - [11/Jun/2014:07:22:03 +0100] "GET /media/css/seahub.css?t=1398068110 HTTP/1.1" 200 59087

212.200.65.133 - - [11/Jun/2014:07:22:03 +0100] "GET /media/js/jq.min.js?t=1398068110 HTTP/1.1" 200 198710

212.200.65.133 - - [11/Jun/2014:07:22:04 +0100] "GET /media/js/base.js?t=1398068110 HTTP/1.1" 200 28778

212.200.65.133 - - [11/Jun/2014:07:22:04 +0100] "GET /media/custom/logo.png HTTP/1.1" 200 5187

212.200.65.133 - - [11/Jun/2014:07:22:04 +0100] "GET /media/custom/custom.css HTTP/1.1" 200 204

212.200.65.133 - - [11/Jun/2014:07:22:04 +0100] "GET /media/css/font/fontawesome-webfont.woff?v=3.0.1 HTTP/1.1" 200 43572

212.200.65.133 - - [11/Jun/2014:07:22:04 +0100] "GET /media/img/nav.png HTTP/1.1" 200 3087

212.200.65.133 - - [11/Jun/2014:07:22:04 +0100] "GET /media/img/bg.png HTTP/1.1" 200 9139

212.200.65.133 - - [11/Jun/2014:07:22:05 +0100] "GET /media/css/sf_font/seafile-font.woff HTTP/1.1" 200 2172

212.200.65.133 - - [11/Jun/2014:07:22:05 +0100] "GET /media/img/favicon.png?t=1398068110 HTTP/1.1" 200 1150

212.200.65.133 - - [11/Jun/2014:07:22:05 +0100] "GET /accounts/login/?_=1402467910155 HTTP/1.1" 200 11529

81.142.39.22 - - [11/Jun/2014:07:26:41 +0100] "GET /api2/repos/ HTTP/1.1" 200 872

212.200.65.133 - - [11/Jun/2014:07:28:30 +0100] "-" 408 -

212.200.65.133 - - [11/Jun/2014:07:30:05 +0100] "-" 408 -

[Michele Innocenti]

Il giorno lunedì 9 giugno 2014 18:18:00 UTC+2, Александар Васиљевић ha scritto:

HI,

I cant log in with android client. I get no error. 

Log in button just grays out.

win client works well, and web interface works without problems. 

I have reinstalled the app and the seafile version is 3.0.2.

This is not a real solution, but I also had problems that I could not solve with the Android client.
The only thing I could do is remove the application data, uninstall and reinstall the application.
So if you have not already tried, try to delete the application data before removing it.

[Александар Васиљевић]

Hi Michele, 

Thnaks for your answer, but already did that. I cant log on from several phones, and I have three more servers that i can log on. One windows and two linux servers version 3.0.2 an above. I don't get it everything else works fine. 

--
You received this message because you are subscribed to a topic in the Google Groups "seafile" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/seafile/sWqTgPvEHvo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to seafile+u...@googlegroups.com.

To post to this group, send email to sea...@googlegroups.com.
Visit this group at http://groups.google.com/group/seafile.
For more options, visit https://groups.google.com/d/optout.

--

S poštovanjem,

Aleksandar Vasiljević

administrator softvera

aca@ef.uns.ac.rs

38124628041 38162474511

INDOK Centar, IT Sektor

Ekonomski fakultet u Subotici

Univerzitet u Novom Sadu

[Michele Innocenti]

Il giorno mercoledì 11 giugno 2014 14:12:58 UTC+2, Александар Васиљевић ha scritto:

Hi Michele, 

Thnaks for your answer, but already did that. I cant log on from several phones, and I have three more servers that i can log on. One windows and two linux servers version 3.0.2 an above. I don't get it everything else works fine. 

So it looks like a server problem.
is the first installation on the server or did you do an update?

Try:
http://serverfault.com/questions/383290/too-many-408-error-codes-in-access-log

[Александар Васиљевић]

Hi Michele,

Thank you for your answer.

Apache server is the first installation. Seafile Server was upgraded to version 3.0.2 but this problem happened before upgrade. 

Tried the solution from the link it didnt work also. Even extended timeout period to 600. Still the same.

[Shuai Lin]

In the log I see another ip address "81.142.39.22" visiting the "/api/" url and get a good 200 OK response. Is it a desktop client, or anther mobile device? Why does this ip address seem to be in another subnet?

[Александар Васиљевић]

Hi Shuai Lin,

Thanks for your answer.
We are accessing this server form different devices and dirfferent countires. Thats why there is difference. That one was from a windows client.,

In the meantime I narrowed the problem down to the SSL certificate. I don't know why but only android client, I cant confirm for iphone client have the problem with the installed certificate. I need to figure out now why is the certificate bad for the mobile client when it works well with other clients, or get the new certificate.

Thanks again. 

[Александар Васиљевић]

Hi, 

Solved in the end by recreating certificate files.

Thanks for the help. 

Best regards,

Aleksandar Vasiljevic

[Eric Sietsema]

What do you mean you recreated the certificate files? Did you have to simply delete and recreate the files on the SeaFile server or did you have to recreate the certificates issued and replace the old files with the new ones?

[Александар Васиљевић]

My intermediate certificate file wasn't good. I didn't copy it well or something like that.

I would check my certificates again. Especially check if you've downloaded correct intermediate file. 

20.02.2015. 14.58, "Eric Sietsema" <ericsi...@gmail.com> је написао/ла:

What do you mean you recreated the certificate files? Did you have to simply delete and recreate the files on the SeaFile server or did you have to recreate the certificates issued and replace the old files with the new ones?

--
You received this message because you are subscribed to a topic in the Google Groups "seafile" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/seafile/sWqTgPvEHvo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to seafile+u...@googlegroups.com.