-
Notifications
You must be signed in to change notification settings - Fork 70
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
Incorrect Port After Login and Logout #40
Comments
You need to configure the nginx proxy properly like shown here: https://www.icescrum.com/documentation/reverse-proxy/#proxy_2 (take a look at proxy_set_header lines) |
Thank you for your feedback, but Nginx Proxy Configuration is already been set as per the documentation, below are snapshots of the current configurations (Using upstreams in Nginx for multi-node setup) but currently only using one node. I have even added the I would like to highlight that it is working fine all through the application, except for only the Login and Logout are redirecting to different ports.
Nginx Config: |
I discovered that it is related to the ending of the link. The default application redirection was without the Although the |
Thank you for this detailed feedback. We will take a look ASAP based on your report |
|
HTTPS Port (I am using different ports): Although the following is not related, but just to be in the safe zone to eliminate any doubts if the issue was caused by Nginx. During my experimentation, I made both ports the same for external and Nginx to be Root URL: In Also tried also putting: |
I am wondering if this somehow could be related to the internal Apache Tomcat that is shipped with icescrum. As I did not change any of its configurations yet. |
Hi, Thank you for all these insights. Sorry for the late reply, we have to prioritize customer support over community support, but we did not forget about you! We managed to reproduce your issue, here are some observations:
Anyway, there are several workaround:
|
Hi, After further investigations, it is Tomcat that is acting weirdly, as you suspected in the first place! Thus, I corrected my previous answer. To solve that, we can add a new configuration parameter to docker (and the .jar) to specify the external port when using a https connexion. |
When using custom ports (e.g. 5200, 6000, 10000 ...etc.).
The application works fine for all URL directions except during the following actions:
Then, the application redirect the user to a URL without keeping the custom port, and by default it will go to the default port (443 in HTTPS, and 80 in HTTP).
And the user will need to re-enter the port number again and refresh the page in order for them to access the system.
The issue was experienced in the Dockerized image with Nginx proxy server, I did not try it on the direct JAR installation.
Versions where the issue was experienced 7.45 and 7.46. I did not try it on different versions.
The text was updated successfully, but these errors were encountered: