Skip to content

Fixes for the server reachability test. #3388

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

Merged
merged 1 commit into from
Jan 8, 2024

Conversation

jlesage
Copy link
Contributor

@jlesage jlesage commented Dec 14, 2023

  • Do not apply HTTPs redirection for challenge used by the test.
  • Set the User-Agent to avoid 403 answer from site24x7.com.
  • Handle JSON parsing failure of the received body.
  • Better handling of different error cases.

- Do not apply HTTPs redirection for challenge used by the test.
- Set the `User-Agent` to avoid 403 answer from site24x7.com.
- Handle JSON parsing failure of the received body.
- Better handling of different error cases.
@jlesage jlesage force-pushed the reachability-test-fix branch from b2a8972 to 388fff8 Compare December 19, 2023 22:22
@nginxproxymanagerci
Copy link

Docker Image for build 2 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-3388

Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes.

@jc21 jc21 merged commit bc8211a into NginxProxyManager:develop Jan 8, 2024
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

Successfully merging this pull request may close these issues.

2 participants