Allow remote Access without "bad request" #113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Is this enough to make the Admin page reachable through HTTPS? Or do you also need to generate a custom certificate? |
|
The page is automatically accessible via HTTPS. |
|
Did you check if this certificate is present in the image? Is it automatically generated by the package? |
|
Any news @ka-vaNu ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In my installation, the call always failed due to an HTTP error “Bad Request”. Adding the ServerAlias line (as described in https://www.ugg.li/cups-meldet-bad-request-bei-ssl-auf-ipfqdn/ ) solved the problem.