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

[BUG] SSL IP:PORT never reported as Up in uptime #7

Closed
danmed opened this issue May 23, 2023 · 3 comments
Closed

[BUG] SSL IP:PORT never reported as Up in uptime #7

danmed opened this issue May 23, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@danmed
Copy link

danmed commented May 23, 2023

Describe the bug
Uptime false down when internal URL is SSL with no certificate

To Reproduce
Steps to reproduce the behavior:

Create a subdomain to an internal service that is being served over SSL but does not have a certificate applied.

https://192.168.1.4.443 for example

Have a valid SSL certificate uploaded to Zoraxy

Uptime will never report that service as up.

Expected behavior
Service should report as up.

@danmed danmed added the bug Something isn't working label May 23, 2023
@tobychui
Copy link
Owner

I am not sure what you meant.
You will need a SSL certificate to enable https by HTTP protocol design. I guess you mean you are using a self-signed certificate and the uptime monitor show it as offline?

If that is the case, the up-time monitor treats invalid configured SSL certificate as offline by design.

tobychui added a commit that referenced this issue Jun 8, 2023
+ Added X-Forwarded-Proto for automatic proxy detector
+ Split blacklist and whitelist from geodb script file
+ Optimized compile binary size
+ Added access control to TCP proxy
+ Added "invalid config detect" in up time monitor for isse #7
+ Fixed minor bugs in advance stats panel
+ Reduced file size of embedded materials
@tobychui
Copy link
Owner

Hi @danmed, can you confirm if this bug has been fixed in the latest 2.6.4 builds?

@tobychui
Copy link
Owner

Closing this as the original author of this issue is not responding and I cannot reproduce it in local environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants