[Bug]: Shelf does not seem to be able to send emails via Microsoft Office365 SMTP, blocking logins

[LK-RPN]

Contact Details

No response

What happened?

When trying to sign up a new user, the confirmation email does not get sent. I have confirmed the daemon works with the current credentials via a Synology NAS.

There is no error message in the console.

What I get is the following when trying to sign up a new user after running npm run dev:

   <-- GET /login
   --> GET /login 200 498ms
   <-- GET /join?_data=routes%2F_auth%2B%2Fjoin
   --> GET /join?_data=routes%2F_auth%2B%2Fjoin 200 115ms
   <-- POST /join?_data=routes%2F_auth%2B%2Fjoin
   --> POST /join?_data=routes%2F_auth%2B%2Fjoin 204 2s
   <-- GET /otp?email=(my email)&mode=confirm_signup&_data=routes%2F_auth%2B%2F_auth
   --> GET /otp?email=(my email)&mode=confirm_signup&_data=routes%2F_auth%2B%2F_auth 200 122ms
   <-- GET /otp?email=(my email)&mode=confirm_signup&_data=routes%2F_auth%2B%2Fotp
   --> GET /otp?email=(my email)&mode=confirm_signup&_data=routes%2F_auth%2B%2Fotp 200 108ms
   <-- POST /resend-otp?_data=routes%2F_auth%2B%2Fresend-otp
   --> POST /resend-otp?_data=routes%2F_auth%2B%2Fresend-otp 200 1s
   <-- GET /otp?email=(my email)&mode=confirm_signup&_data=routes%2F_auth%2B%2F_auth
   --> GET /otp?email=(my email)&mode=confirm_signup&_data=routes%2F_auth%2B%2F_auth 200 253ms
   <-- GET /otp?email=(my email)&mode=confirm_signup&_data=routes%2F_auth%2B%2Fotp
   --> GET /otp?email=(my email)&mode=confirm_signup&_data=routes%2F_auth%2B%2Fotp 200 146ms

There is no email arriving in my inbox. The daemon is running over Microsoft 365 for Business and has a valid Exchange license.
It's trying to send the email via Microsofts own SMTP server, smtp.office365.com.

This also leads to the following beheaviour:
When trying to sign up again (for example after restarting the server), trying to sign up with an email previously used does not work.

It gives the following error:
"Something went wrong, refresh page and try to signup again."

The console shows the following:

{"level":50,"time":1738831812697,"pid":5004,"hostname":"(hostname)","err":{"cause":{"__isAuthError":true,"name":"AuthApiError","status":422,"code":"user_already_exists","stack":"AuthApiError: User already registered\n    at handleError (C:\\Shelf.nu\\node_modules\\@supabase\\auth-js\\dist\\main\\lib\\fetch.js:69:11)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async _handleRequest (C:\\Shelf.nu\\node_modules\\@supabase\\auth-js\\dist\\main\\lib\\fetch.js:114:9)\n    at async _request (C:\\Shelf.nu\\node_modules\\@supabase\\auth-js\\dist\\main\\lib\\fetch.js:95:18)\n    at async SupabaseAuthClient.signUp (C:\\Shelf.nu\\node_modules\\@supabase\\auth-js\\dist\\main\\GoTrueClient.js:269:23)\n    at async Module.signUpWithEmailPass (C:/Shelf.nu/app/modules/auth/service.server.ts:44:29)\n    at async action (C:/Shelf.nu/app/routes/_auth+/join.tsx:107:9)\n    at async Object.callRouteAction (C:\\Shelf.nu\\node_modules\\@remix-run\\server-runtime\\dist\\data.js:36:16)\n    at async C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4719:19\n    at async callLoaderOrAction (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4785:16)\n    at async Promise.all (index 0)\n    at async defaultDataStrategy (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4644:17)\n    at async callDataStrategyImpl (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4676:17)\n    at async callDataStrategy (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4086:19)\n    at async submit (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:3945:21)\n    at async queryImpl (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:3903:22)\n    at async Object.queryRoute (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:3872:18)\n    at async handleDataRequest (C:\\Shelf.nu\\node_modules\\@remix-run\\server-runtime\\dist\\server.js:196:20)\n    at async requestHandler (C:\\Shelf.nu\\node_modules\\@remix-run\\server-runtime\\dist\\server.js:118:18)\n    at async C:\\Shelf.nu\\node_modules\\@sentry\\remix\\build\\cjs\\utils\\instrumentServer.js:319:30\n    at async file:///C:/Shelf.nu/node_modules/remix-hono/build/handler.js:7:16\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async file:///C:/Shelf.nu/node_modules/remix-hono/build/session.js:19:9\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async logger2 (C:/Shelf.nu/server/logger.ts:46:3)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async file:///C:/Shelf.nu/node_modules/hono/dist/hono-base.js:200:25\n    at async getRequestListener.overrideGlobalObjects (file:///C:/Shelf.nu/node_modules/@hono/vite-dev-server/dist/dev-server.js:69:32)\n    at async responseViaResponseObject (file:///C:/Shelf.nu/node_modules/@hono/node-server/dist/index.mjs:330:15)"},"label":"Auth","additionalData":{"email":"(my email)"},"shouldBeCaptured":true,"status":500,"traceId":"cuntce6liuae6wl6yfqf5q18","name":"ShelfError","message":"Something went wrong, refresh page and try to signup again.","stack":"ShelfError: Something went wrong, refresh page and try to signup again.\n    at Module.makeShelfError (C:/Shelf.nu/app/utils/error.ts:57:12)\n    at action (C:/Shelf.nu/app/routes/_auth+/join.tsx:115:43)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async Object.callRouteAction (C:\\Shelf.nu\\node_modules\\@remix-run\\server-runtime\\dist\\data.js:36:16)\n    at async C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4719:19\n    at async callLoaderOrAction (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4785:16)\n    at async Promise.all (index 0)\n    at async defaultDataStrategy (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4644:17)\n    at async callDataStrategyImpl (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4676:17)\n    at async callDataStrategy (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4086:19)\n    at async submit (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:3945:21)\n    at async queryImpl (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:3903:22)\n    at async Object.queryRoute (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:3872:18)\n    at async handleDataRequest (C:\\Shelf.nu\\node_modules\\@remix-run\\server-runtime\\dist\\server.js:196:20)\n    at async requestHandler (C:\\Shelf.nu\\node_modules\\@remix-run\\server-runtime\\dist\\server.js:118:18)\n    at async C:\\Shelf.nu\\node_modules\\@sentry\\remix\\build\\cjs\\utils\\instrumentServer.js:319:30\n    at async file:///C:/Shelf.nu/node_modules/remix-hono/build/handler.js:7:16\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async file:///C:/Shelf.nu/node_modules/remix-hono/build/session.js:19:9\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async logger2 (C:/Shelf.nu/server/logger.ts:46:3)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async file:///C:/Shelf.nu/node_modules/hono/dist/hono-base.js:200:25\n    at async getRequestListener.overrideGlobalObjects (file:///C:/Shelf.nu/node_modules/@hono/vite-dev-server/dist/dev-server.js:69:32)\n    at async responseViaResponseObject (file:///C:/Shelf.nu/node_modules/@hono/node-server/dist/index.mjs:330:15)"},"msg":"Something went wrong, refresh page and try to signup again."}
  --> POST /join?_data=routes%2F_auth%2B%2Fjoin 500 1s
  <-- GET /join?_data=routes%2F_auth%2B%2F_auth
  --> GET /join?_data=routes%2F_auth%2B%2F_auth 200 143ms
  <-- GET /join?_data=routes%2F_auth%2B%2Fjoin
  --> GET /join?_data=routes%2F_auth%2B%2Fjoin 200 102ms

I redacted all instances of my hostname and email in this for security reasons. So Shelf thinks the user is already registered from what I can read. These users then appear in Supabase under the "Authentication" tab.

When trying to log in with these users, I get the following error:

You do not have access to any organization. Please contact support.

{"level":50,"time":1738842096918,"pid":5004,"hostname":"(hostname)","err":{"cause":null,"label":"Organization","title":"No organization","additionalData":{"userId":"caf5b2ad-940f-47fc-bc97-76440bc15eb0","userOrganizationIds":[]},"shouldBeCaptured":false,"status":403,"traceId":"zr1e5ligxzqjomjwzeb8t2sc","name":"ShelfError","message":"You do not have access to any organization. Please contact support.","stack":"ShelfError: You do not have access to any organization. Please contact support.\n    at Module.makeShelfError (C:/Shelf.nu/app/utils/error.ts:57:12)\n    at action (C:/Shelf.nu/app/routes/_auth+/login.tsx:88:43)\n    at async Object.callRouteAction (C:\\Shelf.nu\\node_modules\\@remix-run\\server-runtime\\dist\\data.js:36:16)\n    at async C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4719:19\n    at async callLoaderOrAction (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4785:16)\n    at async Promise.all (index 0)\n    at async defaultDataStrategy (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4644:17)\n    at async callDataStrategyImpl (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4676:17)\n    at async callDataStrategy (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:4086:19)\n    at async submit (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:3945:21)\n    at async queryImpl (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:3903:22)\n    at async Object.queryRoute (C:\\Shelf.nu\\node_modules\\@remix-run\\router\\dist\\router.cjs.js:3872:18)\n    at async handleDataRequest (C:\\Shelf.nu\\node_modules\\@remix-run\\server-runtime\\dist\\server.js:196:20)\n    at async requestHandler (C:\\Shelf.nu\\node_modules\\@remix-run\\server-runtime\\dist\\server.js:118:18)\n    at async C:\\Shelf.nu\\node_modules\\@sentry\\remix\\build\\cjs\\utils\\instrumentServer.js:319:30\n    at async file:///C:/Shelf.nu/node_modules/remix-hono/build/handler.js:7:16\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async file:///C:/Shelf.nu/node_modules/remix-hono/build/session.js:19:9\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async logger2 (C:/Shelf.nu/server/logger.ts:46:3)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async dispatch (file:///C:/Shelf.nu/node_modules/hono/dist/compose.js:29:17)\n    at async file:///C:/Shelf.nu/node_modules/hono/dist/hono-base.js:200:25\n    at async getRequestListener.overrideGlobalObjects (file:///C:/Shelf.nu/node_modules/@hono/vite-dev-server/dist/dev-server.js:69:32)\n    at async responseViaResponseObject (file:///C:/Shelf.nu/node_modules/@hono/node-server/dist/index.mjs:330:15)"},"msg":"You do not have access to any organization. Please contact support."}
  --> POST /login?_data=routes%2F_auth%2B%2Flogin 403 989ms
  <-- GET /login?_data=routes%2F_auth%2B%2F_auth
  --> GET /login?_data=routes%2F_auth%2B%2F_auth 200 105ms
  <-- GET /login?_data=routes%2F_auth%2B%2Flogin
  --> GET /login?_data=routes%2F_auth%2B%2Flogin 200 102ms

Deleting these users from supabase seems difficult, since it always results in an API error when trying to do so.

What is the expected behaviour?

I get an email.

Version

Self-hosted

What browsers are you seeing the problem on?

Firefox

Relevant log output

[yshah-aromatech]

having the same issue on a new docker production setup, using gmail smtp creds.

No emails are being sent when logging in and the docker logs show no error, neither does the site iteself.

Scheduler and workers registration completed
  <-- GET /
  --> GET / 302 23ms
  <-- GET /login
  --> GET /login 200 34ms
  <-- GET /join?_data=routes%2F_auth%2B%2Fjoin
  --> GET /join?_data=routes%2F_auth%2B%2Fjoin 200 10ms
  <-- POST /join?_data=routes%2F_auth%2B%2Fjoin
  --> POST /join?_data=routes%2F_auth%2B%2Fjoin 204 2s
  <-- GET /otp?email=random%40random.com&mode=confirm_signup&_data=routes%2F_auth%2B%2Fotp
  --> GET /otp?email=random%40random.com&mode=confirm_signup&_data=routes%2F_auth%2B%2Fotp 200 10ms
  <-- GET /otp?email=random%40random.com&mode=confirm_signup&_data=routes%2F_auth%2B%2F_auth
  --> GET /otp?email=random%40random.com&mode=confirm_signup&_data=routes%2F_auth%2B%2F_auth 200 6ms

[LK-RPN]

having the same issue on a new docker production setup, using gmail smtp creds.

No emails are being sent when logging in and the docker logs show no error, neither does the site iteself.

Scheduler and workers registration completed
  <-- GET /
  --> GET / 302 23ms
  <-- GET /login
  --> GET /login 200 34ms
  <-- GET /join?_data=routes%2F_auth%2B%2Fjoin
  --> GET /join?_data=routes%2F_auth%2B%2Fjoin 200 10ms
  <-- POST /join?_data=routes%2F_auth%2B%2Fjoin
  --> POST /join?_data=routes%2F_auth%2B%2Fjoin 204 2s
  <-- GET /otp?email=random%40random.com&mode=confirm_signup&_data=routes%2F_auth%2B%2Fotp
  --> GET /otp?email=random%40random.com&mode=confirm_signup&_data=routes%2F_auth%2B%2Fotp 200 10ms
  <-- GET /otp?email=random%40random.com&mode=confirm_signup&_data=routes%2F_auth%2B%2F_auth
  --> GET /otp?email=random%40random.com&mode=confirm_signup&_data=routes%2F_auth%2B%2F_auth 200 6ms

We also did not get it to work since making this thread. We also double checked if it could maybe be something Supabase related, however the Supabase CLI mail service works fine. The daemon also still works in other applications.

[DonKoko]

Without showing any errors or more detailed logs, I can maybe ask some questions to help you get to it:

1. Have you ran your migrations? If you visit your supabase dashboard, do you see the tables?
2. Email not being received - i don't see anything in the logs for sending the emails? You should get a log entry when sending an email. HAve you added your SMTP details to your app's env variables?
3. @LK-RPN considering you are running a dev build, you can always add some extra logging to see exactly what is happening.

EDIT: I have just done a test sending emails with Office365 SMTP and worked fine. Make sure you enable it in your settings. It wont work unless you have done that.

[LK-RPN]

Hey there @DonKoko ,

After stopping the database and trying to restart it because of the API errors in Supabase I mentioned, Supabase claims that the database is unhealthy and won't start it again. I'm considering just reinstalling the entire thing on Linux to see if that will fix the problems I'm having with Supabase CLI. I did not run any migrations, because I was unsure after what exactly to do after starting it using npm run dev, since I wasn't able to log in in the first place.

I can see tables in Supabase, they were created when first initializing the database. However, none of the tables had entries. The users I created in Shelf were showing up in the "Authentication" tab in Supabase. I created the buckets according to the documentation.

I added the details of the daemon into the .env file for Shelf. I also enabled onboarding emails in the settings.

I will reinstall everything on Linux later today and update you again.

[DonKoko]

After stopping the database and trying to restart it because of the API errors in Supabase I mentioned, Supabase claims that the database is unhealthy and won't start it again. I'm considering just reinstalling the entire thing on Linux to see if that will fix the problems I'm having with Supabase CLI. I did not run any migrations, because I was unsure after what exactly to do after starting it using npm run dev, since I wasn't able to log in in the first place.

I am really not sure about those supabase errors. We dont self-host supabase. You can join their discord, maybe someone there can you you.

I can see tables in Supabase, they were created when first initializing the database. However, none of the tables had entries. The users I created in Shelf were showing up in the "Authentication" tab in Supabase. I created the buckets according to the documentation.

That is expected flow for supabase auth. User only gets created after the email is confirmed.

[LK-RPN]

@DonKoko Thank you for your help and patience so far!

I have now reinstalled the entire thing on Ubuntu, which is performing a whole lot better than the Windows VM. The supabase errors are also fixed now.

I am now facing the same problem from before. I tried it with an Exchange account, as well as an account from Strato. Both do not work. The login UI says "Email sent successfully. Please check your inbox.". The CLI tells me the same things I had sent before. I assume it's not related to Microsoft but to some settings.

So what I did thus far:

I followed the documentation along until the step where you have to run npm run dev for the first time. I have not continued past that point, though I assume that should not impact email sending.

When running npm run dev for the first time I got this error:

error when starting dev server:
Error: error:0480006C:PEM routines::no start line
at node:internal/tls/secure-context:70:13
at Array.forEach ()
at setCerts (node:internal/tls/secure-context:68:3)
at configSecureContext (node:internal/tls/secure-context:191:5)
at Object.createSecureContext (node:_tls_common:114:3)
at Server.setSecureContext (node:_tls_wrap:1488:27)
at new Server (node:_tls_wrap:1352:8)
at new Http2SecureServer (node:internal/http2/core:3178:5)
at createSecureServer (node:internal/http2/core:3389:10)
at resolveHttpServer (file:///home/shelf/shelf.nu/node_modules/vite/dist/node/chunks/dep-CHZK6zbr.js:45560:12)
at async _createServer (file:///home/shelf/shelf.nu/node_modules/vite/dist/node/chunks/dep-CHZK6zbr.js:62933:46)
at async CAC. (file:///home/shelf/shelf.nu/node_modules/vite/dist/node/cli.js:736:20)

I had to generate my own SSL certificates since they were missing, I did not have to do that on my Windows VM though. So I'm not sure if this is intended behaviour. I assume this is because .cert is included in the .gitignore.

In my .env I have the following related to email (I of course changed email and password for privacy reasons but I verified they are correct):

DISABLE_SIGNUP="false"
DISABLE_SSO="false"
SMTP_PWD="my password"
SMTP_HOST="smtp.office365.com"
SMTP_USER="my@email.com"
SMTP_FROM="RPN-SHELF" <my@email.com">
SEND_ONBOARDING_EMAIL="true"
ADMIN_EMAIL="another@email.com"

I also set my maptiler and geocode tokens.

The user is once again generated in Supabase as you mentioned. Though it says the user was confirmed at the same time I sent the first email.

Is there any other setting I missed to set the email settings correctly? Do I need to set up SSO in Microsoft Entra in order for this to work?

I also noticed a 404 error in the documentation, I already made a pull request fixing the dead link.

[DonKoko]

hey @LK-RPN . For some reason this thread got lost on me, and I just found it again. I am wondering if you managed to resolve this?
Based on what I am seeing in the env you sent, it should all work. Keep in mind that the way email sending works is via node-mailer. So it just sends the email using those credentials. It could be that office 365 is blocking it. I know it works like this with gmail. If you try to send using their SMTP, you will get success but on their side they block it unless you do some config. I haven't done this in a long time so I don't remember the details. Maybe its the same for office365.

The user is once again generated in Supabase as you mentioned. Though it says the user was confirmed at the same time I sent the first email.

Have you checked if the requires confirmation setting in supabase is enabled? I am not sure what is the default tbh, but I know they have an option to get users to signup without confirmation required.

[LK-RPN]

Hey @DonKoko

With a colleague we got a bit further, we ran migrations to production and made a build version and all.

But still, I was not able to get it to work unfortunately. The email just landed in inbucket, though I think this is now more of a Supabase CLI error than a shelf error. But even then, I was able to copy the verification code from the email, but when I pasted it into the shelf login I got the following error:

Application Error
$h@http://10.0.30.175:3000/file-assets/pkcvym5k/assets._index-Ct68wF2J.js:76:3187
Uw@http://10.0.30.175:3000/file-assets/pkcvym5k/components-C3T7Hz84.js:194:7108
Fu@http://10.0.30.175:3000/file-assets/pkcvym5k/components-C3T7Hz84.js:38:19518
Sh@http://10.0.30.175:3000/file-assets/pkcvym5k/components-C3T7Hz84.js:40:43918
yh@http://10.0.30.175:3000/file-assets/pkcvym5k/components-C3T7Hz84.js:40:39692
Qv@http://10.0.30.175:3000/file-assets/pkcvym5k/components-C3T7Hz84.js:40:39620
Ki@http://10.0.30.175:3000/file-assets/pkcvym5k/components-C3T7Hz84.js:40:39472
Ya@http://10.0.30.175:3000/file-assets/pkcvym5k/components-C3T7Hz84.js:40:35851
ph@http://10.0.30.175:3000/file-assets/pkcvym5k/components-C3T7Hz84.js:40:34802
P@http://10.0.30.175:3000/file-assets/pkcvym5k/components-C3T7Hz84.js:25:1570
G@http://10.0.30.175:3000/file-assets/pkcvym5k/components-C3T7Hz84.js:25:1937

What could be causing this?

[DonKoko]

This error usually happens with some misconfiguration of env variables or something like this. Can you run a development build (npm run dev) instead so you can see the actual error?
Also do you see something in the browser console or in the server terminal?

[aygrossphotography-hue]

Its broken for me as well