☁️ The Most Secure and Easy Selfhosted Home Server. Take control of your data and privacy without sacrificing security and stability (Authentication, anti-DDOS, anti-bot)
coming from an nginx proxy manager/authelia setup really interested in cosmos as an all in one solution.
initial setup:
i own (with cloudflare DNS) mydomain.com - per the instructions, i set the hostname to mydomain.com
i proxy through cloudflare - i have the api key for let's encrypt
currently use edge cert for a lot of my (15) subdomains (qrcodes.mydomain.com, notes.mydomain.com...)
i understand that cosmos will simply create let's encrypt certs for these
setup finishes, but without adding a LOCAL DNS entry for mydomain.com I cannot access the admin console.
-could we possibly run the admin console on a different port, or possibly enable access by ip address?
What should have happened?
setup process asks you for the domain you want to set the wildcard certs for.
setup process asks you for the 'cosmos-admin-gui' host you want to use. (same host, heck even same port, but you need the right host name to access it'
How to reproduce the bug?
Go to '...'
Click on '....'
Scroll down to '....'
See error
Relevant log output
no logs, just looking for some ideas.
also, any way to add certs to a cert store, and when setting up the app, you can tell it what cert to use (a la NPM)
any way to setup non https proxy? (i'll look in resolved issues for this one)
What happened?
coming from an nginx proxy manager/authelia setup really interested in cosmos as an all in one solution.
initial setup: i own (with cloudflare DNS) mydomain.com - per the instructions, i set the hostname to mydomain.com
setup finishes, but without adding a LOCAL DNS entry for mydomain.com I cannot access the admin console. -could we possibly run the admin console on a different port, or possibly enable access by ip address?
What should have happened?
setup process asks you for the domain you want to set the wildcard certs for. setup process asks you for the 'cosmos-admin-gui' host you want to use. (same host, heck even same port, but you need the right host name to access it'
How to reproduce the bug?
Relevant log output
Other details
No response
System details