You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GeoNode should use the correct proxy URL base from GeoServer, including the specified port, to retrieve REST attributes. Or take a attribute from .env file.
Actual Behavior
I am experiencing an issue where GeoNode is not correctly using the specified port in the proxy URL when accessed externally. Specifically, I am using a DDNS to access GeoNode externally, and I need to include an external port in the DDNS (e.g., http://example.ddns.net:9000) to correctly redirect to my PC.
While everything is functioning properly, the problem arises in the mapstore-client, which retrieves data from the API using a URL derived from the SITEURL parameter in the environment configuration. Unfortunately, the SITEURL parameter does not accept a port number, and modifying the https_port would disrupt the redirects.
As a result, the URL used by GeoNode is missing the port number, leading to issues when loading resources.
Expected Behavior
GeoNode should use the correct proxy URL base from GeoServer, including the specified port, to retrieve REST attributes. Or take a attribute from .env file.
Actual Behavior
I am experiencing an issue where GeoNode is not correctly using the specified port in the proxy URL when accessed externally. Specifically, I am using a DDNS to access GeoNode externally, and I need to include an external port in the DDNS (e.g., http://example.ddns.net:9000) to correctly redirect to my PC.
While everything is functioning properly, the problem arises in the mapstore-client, which retrieves data from the API using a URL derived from the SITEURL parameter in the environment configuration. Unfortunately, the SITEURL parameter does not accept a port number, and modifying the https_port would disrupt the redirects.
As a result, the URL used by GeoNode is missing the port number, leading to issues when loading resources.
In this example, the desired URL should include the port, like this:
Specifications
The text was updated successfully, but these errors were encountered: