Given the condition of having an SSL-enabled Undercloud, the link that the user is presented with contains an invalid port number (13808). There is an example of a bad URL generated[0]. This is the port of the swift proxy server. When using an SSL-enabled Undercloud, this should be represented by the port 443, and use Apache's ProxyPass/ProxyPassReverse directives to forward the connection to the swift proxy server on the backend.
These conditions could indicate why this bug describes an unknown URL, because the client (browser) is sent to a link (that includes a port) that does not exist.
Given the condition of having an SSL-enabled Undercloud, the link that the user is presented with contains an invalid port number (13808). There is an example of a bad URL generated[0]. This is the port of the swift proxy server. When using an SSL-enabled Undercloud, this should be represented by the port 443, and use Apache's ProxyPass/ ProxyPassRevers e directives to forward the connection to the swift proxy server on the backend.
These conditions could indicate why this bug describes an unknown URL, because the client (browser) is sent to a link (that includes a port) that does not exist.
---
[0] https:/ /38.145. 35.132: 13808/v1/ AUTH_fab9374b8f 2746c8949755a3f b45216f/ plan-exports/ overcloud. tar.gz? temp_url_ sig=cdbd0cfcd60 9d1c72231dba05b 21d61e14a26f72& temp_url_ expires= 1511822695