Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change SSL port #254

Open
CarlSinclair opened this issue Dec 5, 2023 · 0 comments
Open

Change SSL port #254

CarlSinclair opened this issue Dec 5, 2023 · 0 comments

Comments

@CarlSinclair
Copy link

Environment: Almalinux 9 installed through sh script. No docker. SQLite.

I'm having trouble enabling SSL for Statping. I want to have it hosted on a subdomain behind a reverse proxy that redirects requests to port 8080 on HTTP. Problem is, this setup entirely breaks when enabling SSL. It starts listening on 443, and I see no possibility of changing the HTTPS port like how it's possible to change the HTTP port. I find it confusing that HTTP requires a reverse proxy while HTTPS requires a regular vhost.

Also, since I'm here, I have a few more (probably obvious) questions.

  1. Sometimes, for seemingly no apparent reason, the page loads entirely blank. Refreshing doesn't fix it, requiring a restart of StatPing.
  2. Sometimes, for seemingly no apparent reason, the setup page shows up. After refilling the info, none of it applies and the previous setup (and login) persists. Is it possible to disable the setup page after setup?
  3. The Android app crashes when attempting to view the users tab, which is presumably how you login. And notifications don't seem to work without logging in. I understand you guys don't maintain the apps, I was just curious if you're aware of any workarounds.
  4. Is it possible to modify the HTML of the page?
  5. Is it possible to change the /login URL for security reasons?
  6. I'm interested in setting up redundancy by installing StatPing on two separate servers. I know I can use DNS round robins and Nginx to route the traffic to both servers, but I can't figure out the database situation to keep it updated simultaneously on both servers. MySQL seems like the obvious choice, but I'd like to avoid it if possible. Perhaps manually syncing the SQLite file periodically and overwriting the older one or whichever one has less data?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant