|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
So it looks like this specific is resolved or was a configuration error? Or at least you're not able to recreate the conditions that lead to the error?
Note that I'm aware (and already complained on the dev list) that Jenkins does a poor job of pointing you to mandatory configuration: In global configuration, you need to configure the canonical URL to Jenkins to prevent basic things from breaking. That's the setting mostly used in persisted URLs, e.g. in email notifications.
However that's not the end: In the case of reverse proxies that make it look like Jenkins is accessed from a different port, host, or protocol, configuration errors of the proxy (not setting Host or X-Forwarded-Proto) or open issues (X-Forwarded-Port, see JENKINS-23294) may break URLs as well.