Bug when using cutom domain.

[umarjamilpc]

Hello, I am getting issue when i access view log on specific cronjob. (Application error: a client-side exception has occurred (see the browser console for more information).).

Also i wanted to know have you patched the vulnerability of the recent next.js and react ?
Link: https://nextjs.org/blog/CVE-2025-66478

[fccview]

Hi!
Do you have any logs on the docker container itself on the server side?

It would help me understand what's going on, you can also use DEBUGGER=true to add more logs if there's none.

I have a feeling this can be sorted out with env variables if it's a custom domain issue, we just need to figure out which one you need specifically!

Re:react/next vulnerabilities, Cronmaster uses a much older version of next and I purposely haven't upgraded to newer versions yet as these vulnerabilities keep popping out, it doesn't affect Cronmaster nor Jotty. Scatola Magica was affected but has been patched on the day the vulnerability was discovered. ♥️ There's also two more discovered on the 11th which I will be addressing soon, they are not as severe so I am not panicking about it, but will be there with next release, it has already been done in the branch that'll go out :)

I'm lucky enough to work with nextjs in my day job, so we are always on top of these things, which means I obviously apply them on my personal projects too haha

[umarjamilpc]

I need to use sub-domain like : (crons.example.com).
Docker environment are this:

  - APP_URL=https://crons.example.com
  - INTERNAL_API_URL=http://localhost:3000

And using reverse proxy (openlitespeed).
These are the following logs as you requested:

2025-12-13T14:43:56.166750361Z ]
2025-12-13T14:43:56.166753747Z MIDDLEWARE - URL Resolution:
2025-12-13T14:43:56.166757174Z INTERNAL_API_URL: http://localhost:3000
2025-12-13T14:43:56.166760640Z APP_URL: https://crons.example.com
2025-12-13T14:43:56.166764207Z request.nextUrl.origin: https://localhost:3000
2025-12-13T14:43:56.166776972Z → Using: http://localhost:3000
2025-12-13T14:43:56.166781280Z MIDDLEWARE - Session Check URL: http://localhost:3000/api/auth/check-session
2025-12-13T14:43:56.176513474Z MIDDLEWARE - Session Check Response:
2025-12-13T14:43:56.176559090Z status: 200
2025-12-13T14:43:56.176607954Z statusText: OK
2025-12-13T14:43:56.176619877Z ok: true
2025-12-13T14:43:56.179796292Z ⨯ TypeError: Invalid URL
2025-12-13T14:43:56.179828664Z at new URL (node:internal/url:806:29)
2025-12-13T14:43:56.179833533Z at rm (/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:4587)
2025-12-13T14:43:56.179846167Z at rD (/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:22552)
2025-12-13T14:43:56.179849965Z at /app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:25097
2025-12-13T14:43:56.179853601Z at AsyncLocalStorage.run (node:async_hooks:346:14)
2025-12-13T14:43:56.179857178Z at Object.wrap (/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:13:16241)
2025-12-13T14:43:56.179860775Z at /app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:24987
2025-12-13T14:43:56.179864322Z at AsyncLocalStorage.run (node:async_hooks:346:14)
2025-12-13T14:43:56.179867879Z at Object.wrap (/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:13:15489)
2025-12-13T14:43:56.179871456Z at rB (/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:24914) {
2025-12-13T14:43:56.179875082Z code: 'ERR_INVALID_URL',
2025-12-13T14:43:56.179878469Z input: 'https://crons.example.com, https://crons.example.com'
2025-12-13T14:43:56.179882026Z }
2025-12-13T14:43:56.191040493Z [SSE] Client client-1765637032960-ol7se7 disconnected. Total clients: 0

[fccview]

Hi, gonna try and look into this for the next release!
Before I dive deep into the codebase, what happens when you don't set the internal API url?

Also what happens if you set it to the same URL as the APP url?

I'd try both combinations, these variables are there to help different setups as I can't control people's specific proxies :)