Self-hosting issues

[Adrianni]

Hi,

I am really struggling with self hosting Puter. I have a custom domain and a reverse proxy (Caddy) in front of my internal network. I have tried Puter with Caddy as reverse-proxy (with certs) to puter (trust proxy set to 2 hops). With no luck. I've tried a lot of different setups. One issue was that puter redirected me to site.site.site.site.puter.domain.ltd.

I also tried to bypass nginx within Puter stack by directing Caddy directly to puter port (exposed in docker) with trust proxy set to 1. No luck here either.

In both cases i had set the variables "static_hosting_domain", "static_hosting_domain_alt", "private_app_hosting_domain" and "private_app_hosting_domain_alt" to my custom domain. in example: "static_hosting_domain": "site.puter.mydomain.ltd",

Could you please improve the guiding to self-hosting? Advancing/improving the installing script would help as well. Maybe with some prompts to input custom domain, if its dev/prod, and maybe if Puter stack should handle the SSL or not.

[Salazareo]

HI @Adrianni we will take a look, the backend server for puter itself doesn't handle the ssl, but the nginx spawne by the docker compose should. likely some missing config there I imagine.

I'll try to take a look and update the guide.

unfortunately I'm not familiar with Caddy, so not too sure, but if you're resolving the dns there then puter would just need to get config for the host headers that are being resolved.

so in this case your "domain" in config should be puter.mydomain.ltd

and would be expected to support *.puter.mydomain.ltd

from there your static hostings should be just subdomains you wanna reserve there

site.puter.mydomain.ltd, app.puter.mydomain.ltd, etc

I'll double check this is working well and update guidelines as needed

[anicoa]

Same problem here with nginx. Ended up to rewrite all hosts in nginx config like this

# Host-Header Rewrite: externe Domain → interne puter.local Domain
map $host $puter_host {
    "desktop.domain.net"             "puter.local";
    "api.desktop.domain.net"         "api.puter.local";
    "puter-app-icons.site.desktop.domain.net"   "puter-app-icons.site.desktop.domain.net";
    ~^(.+)\.desktop\.domain\.net$    "$1.puter.local";
    default                              $host;
}

[Adrianni]

Maybe the nginx layer could be removed from the stack to simplify, and rather instruct how to use your own reverse-proxy (optional) for handling tls?