Hi @Nick.L, thanks for giving Reactive Resume a go and watching the tutorial.

If you could please check the value in your "STORAGE_URL:" on the Reactive Resume container looks like this:
https://cv-store.mydomain.com/default

 

Please let us know if that helps, or show some more of your setup and I'll try to help some more.

 

Cheers

On 4/18/2024 at 2:58 PM, Eurotimmy said:

Hi @Nick.L, thanks for giving Reactive Resume a go and watching the tutorial.

If you could please check the value in your "STORAGE_URL:" on the Reactive Resume container looks like this:
https://cv-store.mydomain.com/default

 

Please let us know if that helps, or show some more of your setup and I'll try to help some more.

 

Cheers

 

 

Thank you for your prompt response.

I encountered an error message after clicking "Download PDF," which I have attached for your reference. I am using a proxy host for both the PUBLIC_URL and STORAGE_URL, and I have updated these URLs from HTTP to HTTPS.

Additionally, the proxy host is configured with SSL; however, I have not enabled the "force SSL" option. Instead, I have simply pointed the proxy host to the appropriate IP and port.


 

On 4/10/2024 at 12:26 AM, icarus69 said:

Thanks, that worked.

Another question I have: because I've listed a lot of different experiences, and because the Experience section is tied to page #1, when exporting the PDF, page #1 is incredibly long.

Is there a way of setting the default page size as A4, so that the page-splitting occurs more normally?

 

@Eurotimmywonder if this feature could be added? It's a real pain trying to guess the correct length of the page in order to export as an A4 size PDF.

Hey @Nick.L

I’d suggest to try using your “http://192.168.x.x:PORT” addresses in the two fields in the Reactive Resume container instead of using the domain names in there.

Hey @icarus69

Sounds like a good feature but it’ll need to be requested of the developer, in GitHub. 

Having trouble getting previews to generate in Browserless: 

 

 

In browserless I have "TOKEN" Variable matching "CHROME_TOKEN" in Reactive Resume. In RR I also have "CHROME_URL" set as "ws://UNRAID-IP:3011" which is port I have browserless on.

Any suggestions?

EDIT: Resolved - I in fact do have fat cheeseburger fingers and mis-typed like a dummy head. Nevermind above... ProTIP: don't fatfinger things like I did. :sigh: LOL

Edited April 24, 20242 yr by blaine07
dummy

9 hours ago, blaine07 said:

ProTIP: don't fatfinger things like I did. :sigh: LOL

 

Gold! Haha

On 4/1/2024 at 4:38 PM, Eurotimmy said:

Thank you @dallus for giving the tutorial a shot!

I only proxy 2 servers... in my tutorial I use the following settings:
Port 3000 - for Reactive Resume V4 Web UI

Port 9004 - for MinIO file storage

 

In NPM - Proxy Hosts (for example):
cv.mydomain.com >> http://192.168.1.200:3000

cv-store.mydomain.com >> http://192.168.1.200:9004

 

Please note:

Due to me not wanting other (public) users being able to create accounts / resumes's I have Disabled the "cv.mydomain.com" proxy host.

This means your "cv-store.mydomain.com" will still serve your completed resume files publicly for those you share the link to.

Unfortunately the docker env. for disabling public account creation doesn't work...

 

 

How is your "cv-store" domain still able to serve your resume files? Or rather, how do you access them if the first proxy is disabled?

If I try to use the url given by Reactive Resume (given in "cv.mydomain...") but enter it as "cs-store.mydomain...", I'm given an "access denied" error.

I have the first proxy disabled and the second enabled, is there anything else I need to do? I have this fully set up and working otherwise

Solved - For whatever reason, there was an Rxv4 folder in my appdata folder that had lost it's owner and was read-only. Wiped it out, reinstalled the container and got the splash page.

 

Hello all...

 

Wanted to spin this up for self-hosting and followed the video guide step by step, however, the Reactive Resume v4 container gets stuck in a boot loop with the following error (looks like it's looking for an AWS instance?) I've double checked all my options to make sure I didn't fat finger anything and don't see anything referring to amz.

 

/app/dist/apps/server/main.js:553
            throw new common_1.InternalServerErrorException(error);
                  ^

InternalServerErrorException: 400
    at StorageService.onModuleInit (/app/dist/apps/server/main.js:553:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Promise.all (index 0)
    at async callModuleInitHook (/app/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected]__@nestjs+platform_k3xx66d35pcgv4we7xkfmupjtu/node_modules/@nestjs/core/hooks/on-module-init.hook.js:43:5)
    at async NestApplication.callInitHook (/app/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected]__@nestjs+platform_k3xx66d35pcgv4we7xkfmupjtu/node_modules/@nestjs/core/nest-application-context.js:223:13)
    at async NestApplication.init (/app/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected]__@nestjs+platform_k3xx66d35pcgv4we7xkfmupjtu/node_modules/@nestjs/core/nest-application.js:100:9)
    at async NestApplication.listen (/app/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected]__@nestjs+platform_k3xx66d35pcgv4we7xkfmupjtu/node_modules/@nestjs/core/nest-application.js:169:33)
    at async bootstrap (/app/dist/apps/server/main.js:14189:5) {
  response: S3Error: 400
      at Object.parseResponseError (/app/node_modules/.pnpm/[email protected]/node_modules/minio/dist/main/internal/xml-parser.js:86:13)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async Client.makeRequestStreamAsync (/app/node_modules/.pnpm/[email protected]/node_modules/minio/dist/main/internal/client.js:476:19)
      at async Client.makeRequestAsyncOmit (/app/node_modules/.pnpm/[email protected]/node_modules/minio/dist/main/internal/client.js:407:17) {
    code: 'UnknownError',
    amzRequestid: undefined,
    amzId2: undefined,
    amzBucketRegion: undefined,
    [cause]: {
      amzRequestid: undefined,
      amzId2: undefined,
      amzBucketRegion: undefined
    }
  },
  status: 500,
  options: {}
}

 

Edited August 24, 20241 yr by CoderJMC

Hi!

I'm having a bit of a problem with my install: the preview of the resume I'm editing is stuck, it doesn't update with my changes, and it's even survived a full reinstall of every package and dependency without the resume it shows actually existing anymore. What could be the cause? Which app is the one actually showing the preview so I can further check its files?

Thanks!

Hey all, was getting this setup and working this weekend and found a fix for blocking public sign ups.

 

Here is the MR https://github.com/Eurotimmy/unraid-templates/pull/11

 

If this doesn't get merged for whatever reason you can add these environment variables to get it working.

 

This blocks new signups

DISABLE_SIGNUPS: true

 

This blocks signins all together
DISABLE_EMAIL_AUTH

Edited February 3, 20251 yr by Rasbandit

I've been going down a rabbithole for a few hours trying to figure this out. 

I had great success running it locally, but when I tried to proxy Minio through Traefik it was simply not working, I couldn't get access no matter what I was trying. I eventually enabled debug logging on Traefik and found it was giving me a content refused error. 

This lead me to a forum on Stackoverflow recommending to set a Minio container variable for MINIO_SERVER_URL as https://my.domain.com:{Web_UI_Port}. 

I have noted that MINIO_SERVER_URL is deprecated but it still worked for me (For now). 

Hopefully this helps someone else

Hello all,

 

Sorry for the possibly dumb question. I am having trouble after following all instructions. After a brand new install, everything seems to be working, but once I go to login I get these errors:

 

Signing in via email is currently disabled by the administrator.

Signups are currently disabled by the administrator.

 

I have tried adding variables like NODE_ENV: production or DISABLE_EMAIL_AUTH: false and none of these work. Am I missing something obvious?

 

On 4/24/2025 at 3:54 PM, uniquelolram said:

Hello all,

 

Sorry for the possibly dumb question. I am having trouble after following all instructions. After a brand new install, everything seems to be working, but once I go to login I get these errors:

 

Signing in via email is currently disabled by the administrator.

Signups are currently disabled by the administrator.

 

I have tried adding variables like NODE_ENV: production or DISABLE_EMAIL_AUTH: false and none of these work. Am I missing something obvious?

 

I know you posted this a while ago but I wanted to provide the fix just in cases someone experiences the same issue in future.

Yes, there's an obvious fix.

In the reactive resume template, click on 'Show more settings' at the bottom and you'll see both DISABLE_SIGNUPS and DISABLE_EMAIL_AUTH are set to 'true'. Set them both to 'false' and you're good to go.

I'm just posting this in case anyone else is curious, but it looks like OIDC is implemented and able to be turned on. I didn't see it on rxresume's feature list on their main webpage but went searching on their github then documentation. I had assumed for a while it didn't have it, but I was wrong. Here are the env variables.
It's from the self-hosting portion the website.
Link

# -- OpenID (Optional) --
# VITE_OPENID_NAME: OpenID
# OPENID_AUTHORIZATION_URL:
# OPENID_CALLBACK_URL: http://localhost:3000/api/auth/openid/callback
# OPENID_CLIENT_ID:
# OPENID_CLIENT_SECRET:
# OPENID_ISSUER:
# OPENID_SCOPE: openid profile email
# OPENID_TOKEN_URL:
# OPENID_USER_INFO_URL:

Edited November 21, 2025Nov 21 by viviolay

if anyone is using garage for their s3 storage, set the storage region to "garage" in the template.

Hey guys,

I am the only one having this issue? Not sure when it came up, but I see app docker having this in log.
Also, navigating to the wepbage I see: {"status":500,"unhandled":true,"message":"HTTPError"}

I haven't changed anything manually, my fault is that I am using latest tag... that will change soon.

Error: Invalid environment variables

at file:///app/.output/server/_libs/_P5hiJZd0.mjs:19152:9

... 7 lines matching cause stack trace ...

at async Object.fetch (file:///app/.output/server/_libs/_BrI1wvhl.mjs:12525:10) {

cause: Error: Invalid environment variables

at file:///app/.output/server/_libs/_P5hiJZd0.mjs:19152:9

at createEnv (file:///app/.output/server/_libs/_P5hiJZd0.mjs:19157:28)

at file:///app/.output/server/_libs/_P5hiJZd0.mjs:96717:13

at ModuleJob.run (node:internal/modules/esm/module_job:413:25)

at process.processTicksAndRejections (node:internal/process/task_queues:103:5)

at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:660:26)

at async loadEntries (file:///app/.output/server/_libs/_BrI1wvhl.mjs:12232:22)

at async startRequestResolver (file:///app/.output/server/_libs/_BrI1wvhl.mjs:12357:20)

at async Object.fetch (file:///app/.output/server/_libs/_BrI1wvhl.mjs:12525:10),

status: 500,

statusText: undefined,

headers: undefined,

data: undefined,

body: undefined,

unhandled: true

}

SOLVED: was using latest tag and docker auto-updated to v5.0.X , last known good version was v4.5.5 , so rolled back to that one and fixed my issues.

Edited February 11Feb 11 by MoldavianRO

II followed the above video and ran into issues once attempting to start the Reactive Resume container:

I had to alter the template container variables for PUBLIC_URL, CHROME_URL, and STORAGE_SECRET_KEY to match the variables shown in the screenshot.