Hi,
I have a small question about a visible problem. The "Startseite" (HTML id home_link) link is showing escaped HTML and I'm unable to find the reason or a fix.
Jira is installed on Debian 9 behind an SSL enabled nginx working as a proxy (Jira listen config added an additional Port 8081 from some knowledge base articles). Everything else is working perfectly.
Any idea how I could fix this ?
Regards
Joerg Bingemer
My change from /opt/atlassian/jira/conf/server.xml (default connector changed to port 8081 and and additional connector using the right hostname and scheme on port 8080):
Hi Jorg,
It looks like you modified the menu template. Normally there is no underline under the t in the menu text "Startseite".
Did you modify the template or translations text?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jeffrey,
I did not modify any template or translation. Where could one modify this, I thought this stuff is inside the jar files ?
Joerg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jorg,
It is possible to modify the JAR files.
However we don' t recommend doing so.
Does the issue occur when you are accessing JIRA without the proxy?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jeffrey,
unfortunately this does not make any difference, just tried using a SSH Tunnel and Port 8081 (see server.xml).
Using http://127.0.0.1:8081 (when forwarding the local port 8081 to the server):
But I talked to someone today that is also using Jira and he knew the problem. It also happens on his installation since the upgrad to 7.7.1. In fact with Jira 7.6 and the exact same nginx proxy config (old server) did not have this issue.
Joerg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joerg,
If you are still having the issue with the proxy.
That means that the issue is not caused by the proxy.
Can you look in the logs for "Modified Files":
Are there any .vm files listed there?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nginx config:
server {
listen 80 default_server;
#listen [::]:80 default_server;
server_name jira.xxx.de;
server_tokens off;
return 301 https://jira.xxx.de$request_uri;
}
server {
# SSL configuration
#
listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;
server_tokens off;
error_log /var/log/nginx/jira_proxy_error.log;
access_log /var/log/nginx/jira_proxy_access.log;
ssl_certificate /etc/ssl/chained/xxx.de.chained.crt;
ssl_certificate_key /etc/ssl/private/xxx.de.key;
ssl_dhparam /etc/ssl/certs/dhparam.pem;
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;";
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS !MEDIUM";
server_name jira.xxx.de;
location / {
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://127.0.0.1:8080;
client_max_body_size 50M;
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.