SolidInvoice

[pierredup]

Name of the Script

SolidInvoice

Script Type

CT (LXC Container)

Does this script support arm64?

arm64 supported

📋 Script Details

SolidInvoice

[pierredup]

Script added in #1971. Please add the Ready For Testing label 🙏🏼

[github-actions]

The SolidInvoice script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/solidinvoice.sh)"
App startup could be slow. Once the app has started, complete the setup wizard via the web interface on first access.

Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

[CerberusStyle]

Install, Web UI and account setup work, update function also working as expected.

[jintakhan]

Cannot be accessed behind HAProxy reverse proxy.

[CerberusStyle]

Cannot be accessed behind HAProxy reverse proxy.

How do you mean, you need to give more information so this can be reproduced,

[jintakhan]

Cannot be accessed behind HAProxy reverse proxy.

How do you mean, you need to give more information so this can be reproduced,

HAProxy frontend is the domain foobar.com. Backend is set to SolidInvoice port and IP. Forward headers such as X-Forwarded-Host etc. do not seem to make a difference. A websocket request from foobar.com is successfully made to the LXC, where SolidInvoice's internal Caddy instance cannot find what to serve. I believe this is because it tries to find resources inside the LXC with the reverse proxy host domain name of foobar.com when the app itself is bound only to the IP address, localhost and loopback.

Manually setting the domain to foobar.com via /etc/solidinvoice/solidinvoice.env causes SolidInvoice to generate an invalid caddyfile and nothing gets served, perhaps because no certificates were specified.

Inspecting the upstream source code, I see that SolidInvoice automatically allows external hosts like reverse proxies to access it when HTTPS is disabled. But since the default env for the script disables HTTPS, I don't know what's causing the failure.

[CerberusStyle]

Ok that's alot more clear so its not a script issue, its a setup issue on your end for your specific setup, if you would like help with that your better off popping on to the discord and starting a help thread and someone maybe able to help you sort this out.

[jintakhan]

No, I'm pretty sure I've set up the reverse proxy right. Seeing the current script just grabs their single file deployment and puts it in an LXC, I think this is an upstream bug, unless the helper script deployment is doing more than that?

[MickLesk]

Should fixed now @jintakhan

[jintakhan]

Thank you @MickLesk yes it works but with a catch. The initial database setup must be done through the reverse proxy itself, not via the LXC IP address given at the end of the installation script. The application will 404 if the database is initially set up with the IP address. Despite the reverse proxy serving HTTPS, the database field will auto-populate with a http:// version of the URL and that will work with the app.

[pierredup]

The initial database setup must be done through the reverse proxy itself, not via the LXC IP address given at the end of the installation script. The application will 404 if the database is initially set up with the IP address.

@jintakhan The setup doesn't store any values in the DB, I don't think it's necessary to the setup through the reverse proxy. During the setup process, you can set the application URL to anything, even when installing through the IP directly. If you can provide some steps that you are doing an maybe some screenshots with the exact issue, then it will help