400 | Error: Please specify QUIRREL_BASE_URL..

[jatidevelopments]

Bug Report

Current Behavior
When deploying to AWS (Fargate) Quirrel doesn't seem to work. It always asks for the QUIRREL_BASE_URL when calling the queue. I tried setting the QUIRREL_BASE_URL with https:// and without.

Input Code

Queue is in path: /api/emailQueue.ts (NextJS):

export default Queue("api/emailQueue", async ({ id }, meta) => {
... 
})

Calling the queue:

emailQueue.enqueue(
          {
            id: r.data.id,
          },
          {
            retry: ["10sec", "60sec", "5min", "15min"],
          }
        )

Expected behavior/code
Pushing to the queue and don't return an error that the QUIRREL_BASE_URL isn't defined.

Environment

• Quirrel version: 1.8.1
• Node/npm version: Node 16

Does anybody know a solution?

[Skn0tt]

hey @jatidevelopments! are you using the hosted Quirrel version (https://quirrel.dev), or a self-hosted instance? could you specify what "it always asks for the QUIRREL_BASE_URL" means? is that a log output you're seeing?

[jatidevelopments]

Hi @Skn0tt we are using the hosted Quirrel version. We deploy on AWS. I can't see anything in the Logsoutput but it happens when I try to call the emailQueue.enqueue function it returns "400 | Error: Please specify QUIRREL_BASE_URL".

[Skn0tt]

Hmm :/ That error is thrown by this line:

quirrel/src/client/config.ts

Line 103 in ba99519

throw new Error("Please specify QUIRREL_BASE_URL.");

It seems to me that somehow your environment variables aren‘t set correctly. Can you verify that QUIRREL_BASE_URL is indeed specified? For example by logging process.env.QUIRREL_BASE_URL right before your .enqueue call.

[jatidevelopments]

Okay, I will test it. Maybe it's because the env is from the Parameter Store at AWS. Do I need to add https:// in front?

[Skn0tt]

Shouldn‘t make a difference. If there‘s no protocol given, it automatically uses https://:

quirrel/src/client/config.ts

Line 106 in ba99519

return normalisedURL(baseUrl);

but specyfing the protocol also works fine.

[jatidevelopments]

Now I get this error locally after switching the import from quirrel/vercel to quirrel/blitz

[Skn0tt]

I assume that you were able to fix the QUIRREL_BASE_URL issue.

That error looks like you specified QUIRREL_ENCRYPTION_SECRET locally, but had pending jobs that weren‘t encrypted at all. So now it‘s trying to decrypt an unencrypted payload. Could that be the case?

[jatidevelopments]

I know the error
We use react-admin for the admin panel
This only works only at client side
So we disabled SSR
Quirrel cant get the QUIRREL_BASE_URL env on client-side
So yeah we need to create an API endpoint and then call the enqueue function in there

So it's solved! But thanks for the support!