• 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
  • 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

Google and twitter login not working on v4.0.0

lovedigit

lovedigit

👽 Chevereto Freak
*️⃣ Must open one ticket per issue. If you are experiencing multiple issues don't hesitate to create multiple tickets for each issue.

▶ Reproduction steps
  1. Try to login with google, twitter or discord
  2. Login fails with error
😢 Unexpected result

According to the v4 documentation, we have to use https://yourwebsite.com/connect for callback or return url.
So, we just have to change the url to this, instead of https://yourwebsite.com/connect/{google|twitter|discord|whatever} in respecting application settings on their app console.
For eg:
1Nlerc.png


However, I am receiving this error, even after waiting for more than 12 hours.

1Nnf8T.png


Same is true for twitter:

1Nn4pH.png


Even though the callback url is set as suggested by documentation:

1NnOBK.png


I waited for the changes to propagate on these services for more than 12 hours but so far it is not working.

📃 Error log message


1Nn4pH.png
 
Yes, facebook works for me too. Didn't test with github yet.
Edit 1: Twitter error is fixed if I enter https://yourwebsite.com/connect/twitter/ (with trailing /) as callback url instead of https://yourwebsite.com/connect.
Edit 2: Google error is also fixed if I enter https://yourwebsite.com/connect/google/ (with trailing /) as callback url.

Having trouble setting up discord as well. If I use the url from discord OAuth2 url generator, I get this error message.
1PiSVD.png


And if I go to yourwebsite.com/connect/discord I get "Invalid OAuth2 redirect url" error.

Edit 3: Ok. "Invalid OAuth2 redirect_url" is fixed if I enter https://yourwebsite.com/connect/discord/ (with trailing /) in the discord app seeting dev console. Trailing / is required because redirect url has it.

Code: 
https://discord.com/oauth2/authorize?response_type=code&client_id=REDACTED&redirect_uri=https%3A%2F%2Fyourwebsite.com%2Fconnect%2Fdiscord%2F&scope=identify+email&state=REDACTED

But after that, I get this error.

1PudG5.png


Edit 4: Discord is fixed too. As mentioned had to enter https://yourwebsite.com/connect/discord/ (with trailing /). But, I was copying the wrong secret key. The discord secret key is located under OAuth2 > general, and not under General information, which has application ID and key as well, but that is not application secret.

Please reflect these changes in documentation. because https://yourwebsite.com/connect doesn't work on all providers. Also, please move it to away from "bug tracking". It is obviously not a bug.
 
Last edited:
🤔 What if you use https://yourwebsite.com/connect/ ?
 
👌 GitHub also works, so yeah it is better to use the full strict url. I will update the docs.
 
You must log in or register to reply here.
Back
Top