• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space

If Logout clicked server returns 404

Status
Not open for further replies.
Skotina

Skotina

Chevereto Member
Hello,

After 3.5.2 update found out that I can't logout - when I hit corresponding button server returns 404 error.
I've uploaded all necessary files (I hope) so I can't find the spot with error.

Site is upics.ru
 
Logout is working fine for me in the demo, have you modified your website?
 
It could be caused by that. Try with a test clean install.
 
I guess the problem is not with edited files.
I found out that sometimes "/" is added at the end of the URL and this causes 404.
You can try http://upics.ru/image/xJ and then http://upics.ru/image/xJ/ - the latest will return 404 error. I checked nginx error log and the url that returns error also has "/" at the end before token and I believe it shouldn't be there.

Code: 
2014/10/11 12:43:59 [error] 6393#0: *290338 "/var/www/vhosts/upics.ru/httpdocs/logout/index.html" is not found (2: No such file or directory), client: 178.217.104.142, server: upics.ru, request: "GET /logout/?auth_token=TOKENHERE HTTP/1.1", host: "upics.ru", referrer: "http://upics.ru/"

I am not sure that this problem is caused by chevereto, maybe its nginx? It is searching for index.html file which isn't here actually (and can't be there).
 
I've setup fresh Chevereto install and it has no these problems.
Rodolfo, can you help with this? At least show which way I should dig to find the problem.
 
Rodolfo, please close the topic.
The problem was with nginx config - if the trailing slash was present it was searching for the index file.
Logout problem was also fixed.
 
The system always try to normalize the URL. By the way, it worked with the ngix rules that I've in the documentation?
 
Status
Not open for further replies.
Back
Top