Typebot with Cloudron login does not work
-
Hello,
I installed Typebot and when I did the install I said to allow Cloudron login. When I go to Click on Login with Cloudron after the setup is done, it fails. Here are the logs:
Jan 05 10:33:09[next-auth][error][SIGNIN_OAUTH_ERROR]
Jan 05 10:33:09error: {
Jan 05 10:33:09https://next-auth.js.org/errors#signin_oauth_error outgoing request timed out after 3500ms {
Jan 05 10:33:09message: 'outgoing request timed out after 3500ms'
Jan 05 10:33:09message: 'outgoing request timed out after 3500ms',
Jan 05 10:33:09name: 'RPError'
Jan 05 10:33:09providerId: 'custom-oauth',
Jan 05 10:33:09stack: 'RPError: outgoing request timed out after 3500ms\n' +
Jan 05 10:33:09}
Jan 05 10:33:09},
Jan 05 10:33:17' at /app/code/builder/node_modules/.pnpm/openid-client@5.6.0/node_modules/openid-client/lib/helpers/request.js:137:13\n' +
Jan 05 10:33:17' at async AuthHandler (/app/code/builder/node_modules/.pnpm/next-auth@4.22.1_next@14.0.3_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/index.js:260:26)\n' +
Jan 05 10:33:17' at async Issuer.discover (/app/code/builder/node_modules/.pnpm/openid-client@5.6.0/node_modules/openid-client/lib/issuer.js:144:24)\n' +
Jan 05 10:33:17' at async NextAuthApiHandler (/app/code/builder/node_modules/.pnpm/next-auth@4.22.1_next@14.0.3_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/next/index.js:22:19)\n' +
Jan 05 10:33:17' at async Object.signin (/app/code/builder/node_modules/.pnpm/next-auth@4.22.1_next@14.0.3_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/routes/signin.js:38:24)\n' +
Jan 05 10:33:17' at async getAuthorizationUrl (/app/code/builder/node_modules/.pnpm/next-auth@4.22.1_next@14.0.3_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/lib/oauth/authorization-url.js:70:18)\n' +
Jan 05 10:33:17' at async openidClient (/app/code/builder/node_modules/.pnpm/next-auth@4.22.1_next@14.0.3_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/lib/oauth/client.js:16:14)\n' +
Jan 05 10:33:17' at async y (/app/code/builder/apps/builder/.next/server/chunks/162.js:1:7850)',
Jan 05 10:33:17[next-auth][error][SIGNIN_OAUTH_ERROR]
Jan 05 10:33:17error: {
Jan 05 10:33:17https://next-auth.js.org/errors#signin_oauth_error outgoing request timed out after 3500ms {
Jan 05 10:33:17message: 'outgoing request timed out after 3500ms'
Jan 05 10:33:17message: 'outgoing request timed out after 3500ms',
Jan 05 10:33:17name: 'RPError'
Jan 05 10:33:17providerId: 'custom-oauth',
Jan 05 10:33:17stack: 'RPError: outgoing request timed out after 3500ms\n' +I don't know if I am doing something wrong, but this is the first Cloudron app that is giving me problems. Thanks!
-
-
@girish I tried surfer and got the following when I sent to the URL with /_admin as per the first setup instructions for the admin panel:
{"status":"Internal Server Error","message":"Issuer.discover() failed.\n RequestError: Timeout awaiting 'request' for 5000ms\n RequestError: Timeout awaiting 'request' for 5000ms"}
I did not even get the option to login in. Then I click the back button and it took me to the option to login with Cloudron and then I signed me in with no issues.
Note, my server is hosted internally on my own equipment and I have a IP from a /28 from my ISP that I use with GoDaddy to access everything.
As for the question of openid Login, I do not have that option
-
@skeats I should have been clearer. OpenID login is where the app is doing authentication via Cloudron . Typebot, Surfer use this. For this to work, the app needs to access
https://my.example.com
(i.e the dashboard URL). Looks like this is not working in your setup.To debug:
- Open a Web Terminal for Surfer
host my.example.com
- does this work? (replace example.com with your dashboard domain)curl https://my.example.com
- does this work ?
-
@skeats said in Typebot with Cloudron login does not work:
curl: (28) Failed to connect to my.example.com port 80 after 130794 ms: Connection timed out
right, so this is the core of the issue. You need to investigate why the server is not able to curl itself. I assume you can curl from another device/laptop in the same network, correct ?