[Bug] <can not export a pdf resume ,a about:blank window pops up every time I click the issue is not working for me>

[Rickustc]

Is there an existing issue for this?

• Yes, I have searched the existing issues and none of them match my problem.

Product Variant

Cloud (https://rxresu.me)

Current Behavior

can not export a pdf resume ,a about:blank window pops up every time I click the issue is not working for me

Expected Behavior

No response

Steps To Reproduce

No response

What browsers are you seeing the problem on?

No response

What template are you using?

None

Anything else?

No response

[Rickustc]

win 11 + firefox /edge /chrome has been tried

[Normanras]

Just confirmed that this is happening for me as well, but I'm running a self-hosted version without a FQDN. Not sure if that matters (didn't see anything in docs), but just sharing for viz. Also, looks like this is related to #1973 and this comment in #1964. There's actually a bunch of issues if you search of is:open download, but not sure if they are all related - I didn't click through all of them.

[nate235]

Yep, same issue here on self-hosted. Is there a way around this? Of course this happens when I need to send someone a resume lmao

[vietanhdev]

Same issue here.

[00TaciTa00]

Does your resume have non-English or non-numeric characters in the title? In my case, the same thing happened when I titled it in Korean. I changed it to English and it worked.

• Translated by translator.

[YosypC]

After having decided to manually rebuild it again, character by character, I attempted to import the JSON from the broken file. I can say not only the JSON being valid, but it successfully imported it and make a working PDF.

So, the workaround is exporting a JSON (which you should always have), and importing it again.

[Normanras]

@YosypC I tried this thinking maybe it would crazily work... sadly it didn't. Are you (and same question to you, @00TaciTa00 !) on the cloud or self-hosted version? I don't think it should matter, but just want to check.

[YosypC]

@Normanras web

[vietanhdev]

@YosypC @Normanras
I resolved my issue by fixing the network connection from inside Docker.

• docker exec into chromium container.
• Check if you can wget your web.
• Check and fix the firewall / Docker config if you cannot wget.

[Normanras]

@vietanhdev What do you mean by 'wget your web'? I can see that the chromium container is on the same network with the app/s3/db containers. Obviously, no port associated with that container as the compose file doesn't indicate this either.

[vietanhdev]

In my deployment, I separated them so they are not like on the same machine.

[JackTyson]

I was able to fix this issue by doing the following:

1. Set the network_mode option to "host" for all containers.
2. Remove the manually defined "ports" for each container.
3. Change the default port for the RxResume app to 3001 (3000 is used by chrome).
4. Modify the addresses in the docker compose file to reference localhost (or 127.0.0.1) as the address, instead of the container hostname. For example, change the lines "DATABASE_URL: postgresql://postgres:postgres@postgres:5432/postgres" to "DATABASE_URL: postgresql://postgres:[email protected]:5432/postgres" and "CHROME_URL: ws://chrome:3000" to "CHROME_URL: ws://127.0.0.1:3000".

I have not had an issue with it since changing the configuration.

[00TaciTa00]

@Normanras
A little late, web.