• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • This community is user driven. Be polite with other users.
    • We recommend purchasing a Chevereto license to participate in this community.
    • Purchase a Community Subscription to get even faster ticket response times.
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

Can't delete old users

lovedigit

lovedigit

👽 Chevereto Freak
▶ Reproduction steps
  1. Not sure how to replicate it, or if it is just me. I suspect it is same bug related to album. I am able to delete new users, but can't delete older user accounts.
😢 Unexpected result


I get the same trace route on both of these bugs.
When I try to delete an old user, I get this error in console, and when I click on https://domain.com/json, it shows me traceroute in "Error log message" below.
If it is server side issue, I do not know what caused this issue, because I am using the same VPS since last 4 years. Didn't change a single thing, except upgrading it to allocate more resources. I saw php session permissions, and they're fine. The php user:group has read and write access to session folder.
I verified that when I try to delete new accounts, this error doesn't occur. How can server side auth token expiration be partial to only old users, and yet work with new user deletions?
343_Rswj1iUfUu.png


I suspect it is similar bug or somewhat related to album bug that Rodolfo identified in my previous post. When I try to move an album into another album, I get this error in console. And it shows same trace route.
344_f9FxhkvDmi.png

If I am way out of track. Can you indicate what might be causing it? What to look for. Because I check all the permissions and settings on nginx and php. There is nothing I can find in error log as well.

📃 Error log message

Fatal error [400]: Request denied (auth_token)
Triggered in /app/routes/route.json.php at line 22

Stack trace:
#0 /lib/G/classes/class.handler.php(235): G\Handler->{closure}()
#1 /lib/G/classes/class.handler.php(135): G\Handler->processRequest()
#2 /app/web.php(478): G\Handler->__construct()
#3 /app/loader.php(299): require_once('/app/web.php')
#4 /index.php(20): include_once('/app/loader.php')
 
I cannot delete users specially with social media account connected to their profile for login.
I think this is a bug, rather than server misconfiguration. Otherwise, why would I be able to delete other users, and auth token expires only on select few.
I have been cleaning old accounts which are inactive or where temporary email was used to register an account.
And I can delete users, but some accounts would throw an error when attempted to be deleted. If it was server misconfiguration, wouldn't it happen for every deletion?
 
Last edited:
lovedigit said:
when I click on https://domain.com/json, it shows me traceroute in "Error log message" below.
Click to expand...
That's no error at all, that's normal. That's expected. Any call to /json requires the auth_token so is not failing at all. You are misunderstanding the system. You don't need to follow the location, you need to dig the request made. You are just sending another request to the system, not debugging the actual request.

I just deleted some users with social login at demo and it was success. Either this got already covered (demo runs 3.19, yours doesn't) or is not possible to narrow it down with the info you have just provided.
 
Rodolfo said:
That's no error at all, that's normal. That's expected. Any call to /json requires the auth_token so is not failing at all. You are misunderstanding the system. You don't need to follow the location, you need to dig the request made. You are just sending another request to the system, not debugging the actual request.

I just deleted some users with social login at demo and it was success. Either this got already covered (demo runs 3.19, yours doesn't) or is not possible to narrow it down with the info you have just provided.
Click to expand...
How do I debug this then? I will appreciate any pointers.
It doesn't log anything in nginx or php error_logs. And it doesn't happen with all accounts. It doesn't show any trace route.
Is it ok if I send you a screen recording as a DM?
Maybe you're right. It might already is fixed in 1.19. Because I get very similar issue while moving album, i.e. no logs in anywhere, just the same route error in console, and that's it.

Without error log it is hard to pin point what is going on. I will wait for 1.19 release and report back.
 
lovedigit said:
How do I debug this then? I will appreciate any pointers.
Click to expand...

Debug | V3 docs

Documentation for Chevereto V3
v3-docs.chevereto.com v3-docs.chevereto.com

It will be always frustrating for you unless you shift your attitude towards detection rather than interpretation. That's why you spent time debugging a totally different request rather than the actual request needed to be checked and you even reported that as a bug. That lead you to test "GET /json" expecting to find the error cause for a previous "POST /json" with data.

Before 3.19 all error logging depends on your server settings, the application doesn't control that. Perhaps that's why you are missing logs or perhaps sessions are just expiring.

At this point I can't say anything due the lack of information, will close this to handle it under 3.19.beta.1 (if happens).
 
You must log in or register to reply here.
Back
Top