puter
puter copied to clipboard
Multiple domains and access via IP address
Currently the biggest pain-point of self-hosting Puter is the need to setup a domain name.
Some specific examples of the inconvenience:
- #193 - might be config mismatch, but not sure
- #199 - necessary to specify public port in config
- #204 - login error ("blank red box"), likely config mismatch
- #211 - init gui error ("blue page"), might be config mismatch
- #221 - when using Cloudflare, users literally pay for this
- #229 - necessary to set domain in config.json
We can solve this by:
- Add a mode where
api.subdomain is replaced with/apiroute - Also allow
api.to be a different domain - Allow multiple domains
- default configuration allows all domains
- maybe optionally enable an includeslist
Some hurdles/considerations:
- puter.js and GUI both need to be updated to work with either
api.or/api
Is there any updates now?
Is there any updates now?
So far we've added a config option to remove the requirement of a api. subdomain:
"experimental_no_subdomain": true,
Is there any updates now?
So far we've added a config option to remove the requirement of a
api.subdomain:"experimental_no_subdomain": true,
Thanks, the problem has been solved.
But another issue happend, and I think it's the same problem. I can not open https://dev-center.puter.xxx.com。
But another issue happend, and I think it's the same problem. I can not open https://dev-center.puter.xxx.com。
The Dev Center is not yet available on self-host. It's planned though.
OK, when will be ready?
I'm not sure if this issue is related to that one, but every app I've created get its expired subdomain after a while even if other users are using it as I can see in discord, shall I open a new ticket?
What could trigger that issue:
- Changing domain name in other apps,
- Create a new app on existing one (not the one that gets expired subdomain),
- Not opening that app for a couple of days?
Hi @bitsnaps please do open a new issue. This is very bad we need investigate it.
This is no longer an issue: 3666b9f3a25127909940c988164ff61ec3c2ea99
So far we've added a config option to remove the requirement of a
api.subdomain:"experimental_no_subdomain": true,
@KernelDeimos is this option still valid? I put it into my config but still the api domain is used.