Why am I failing to access jasperserver through NGINX as a reverse proxy?

0

Hello team,

We have a jaspersoft installed for reporting purposes. Auditors have raised security concerns as the reports were being accessed through Internet with a vulnerable protocal http that passes info in clear text. They suggested to apply ssl encryption. Jaspersoft is running on Centos7 as OS. To fix the issues raised, I decided to install NGINX to act as a reverse proxy for tomcat to see first whether I will be able to access the jasperserver through nginx and thereafter I apply the ssl certificate.

However, after the installation and configuration of nginx I am getting the error message from the jasperserver be it on nginx access logs and on the browser when I try to access the webserver.

NGINX ACCESS LOGS OUTPUT

===============================

 192.168.1.126 - - [19/Apr/2018:09:04:05 +0200] "GET /jasperserver/optimized-scripts/bower_components/requirejs/require.js HTTP/1.1" 404 47536 "http://192.168.1.128:8083/jasperserver/login.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0"
192.168.1.126 - - [19/Apr/2018:09:04:05 +0200] "GET /jasperserver/_themes/7D17F9B2/overrides_custom.css HTTP/1.1" 404 47536 "http://192.168.1.128:8083/jasperserver/login.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0"
192.168.1.126 - - [19/Apr/2018:09:04:05 +0200] "GET /jasperserver/scripts/bower_components/jquery-ui/themes/redmond/jquery-ui-1.10.4-custom.css HTTP/1.1" 404 47536 "http://192.168.1.128:8083/jasperserver/login.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0"
192.168.1.126 - - [19/Apr/2018:09:04:05 +0200] "GET /jasperserver/optimized-scripts/require.config.js HTTP/1.1" 404 47536 "http://192.168.1.128:8083/jasperserver/login.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0"
192.168.1.126 - - [19/Apr/2018:09:04:05 +0200] "GET /jasperserver/optimized-scripts/bower_components/jquery/dist/jquery.js HTTP/1.1" 404 47536 "http://192.168.1.128:8083/jasperserver/login.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0"
192.168.1.126 - - [19/Apr/2018:09:04:05 +0200] "GET /jasperserver/scripts/bower_components/prototype/dist/prototype.js HTTP/1.1" 404 47536 "http://192.168.1.128:8083/jasperserver/login.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0"
192.168.1.126 - - [19/Apr/2018:09:04:05 +0200] "GET /jasperserver/optimized-scripts/bower_components/requirejs/require.js HTTP/1.1" 404 47536 "http://192.168.1.128:8083/jasperserver/login.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0"
192.168.1.126 - - [19/Apr/2018:09:04:05 +0200] "GET /jasperserver/optimized-scripts/require.config.js HTTP/1.1" 404 47536 "http://192.168.1.128:8083/jasperserver/login.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0"
192.168.1.126 - - [19/Apr/2018:09:04:05 +0200] "GET /jasperserver/optimized-scripts/bower_components/jquery/dist/jquery.js HTTP/1.1" 404 47536 "http://192.168.1.128:8083/jasperserver/login.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0"
192.168.1.126 - - [19/Apr/2018:09:04:05 +0200] "GET /jasperserver/scripts/bower_components/prototype/dist/prototype.js HTTP/1.1" 404 47536 "http://192.168.1.128:8083/jasperserver/login.html" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0"

ERROR MESSAGE ON THE BROWSER SIDE 

===================================

 

Page Not Found

Specified page not found

About TIBCO JasperReports Server

 

Organization

 

Full Name

 

Full Name

 

Organization

 

Name:

 

Path:

 

Save As

    Please Wait

    Loading…

    Error Details

    Heartbeat Data Collection

    Please help us build better products by opting in to the Heartbeat.

    By allowing the Heartbeat to collect data, you confirm consent, where relevant, from all individual users in your organization.

    The Heartbeat enables TIBCO Jaspersoft to collect anonymous system information and may be disabled at any time. The Heartbeat data is used for the purposes set forth in the TIBCO Jaspersoft Heartbeat Privacy Policy web page at www.jaspersoft.com/heartbeat.

    Our privacy policy is at www.jaspersoft.com/privacy.

    About TIBCO JasperReports Server

    Product Version: 6.2.1

    Build: 20160330_2253

    Can someone help me to find out what would be an issue please?

    The configurations made on nginx

    ==========================

    upstream tomcat_server {
            # Tomcat is listening on default 8080 port
            server 127.0.0.1:8080 weight=100 max_fails=5 fail_timeout=5;
        }
    server { listen       8083;
              server_name  192.168.1.128 localhost;

    #         ssl on;
    #         ssl_session_timeout 5m;
    #         ssl_protocols SSLv2 SSLv2 TLSv1;

    #         ssl_certificate /etc/pki/tls/certs/ca.crt;
    #         ssl_certificate_key /etc/pki/tls/private/bi.key;

              root         /opt/jasperreports-server-cp-6.2.1/apache-tomcat/webapps/jasperserver;
              access_log /var/log/nginx/access.log;

    #         index  index.html index.htm index.xml;
    #         ssl_session_cache shared:SSL:10m;
    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://localhost:8080/jasperserver/;
     }
    }
     

    The configurations made on tomcat

    ==========================

    <Connector port="8080" URIEncoding="UTF-8" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8083" proxyName="localhost" proxyPort="8083" scheme="http"/>
     

    Best regards,

    usfrank02's picture
    Joined: Apr 19 2018 - 12:13am
    Last seen: 1 year 2 months ago

    2 Answers:

    0

    Hi Frank,

    I set it up some time ago so cannot remember much but one thing is for sure, you do not have any issues with jasper in this case, you will have to fiddle with nginx to make it work. I would suggest the following to rule certain out certain possibilities,

    - point to google rather than jasper and see if you can reach it (if you can't you know it's nginx issue)

    - assuming you have both nginx and tomcat on the same server, try reaching jasper via browser on the same server (this will definintely get you to the core of the issue)

    - try accessing jasper directly on port 8080 form the browser on the same server to ensure it is up and running

    Thanks.

     

    m.kamran's picture
    141
    Joined: Nov 3 2017 - 3:11am
    Last seen: 1 year 2 months ago
    0
    swood_1's picture
    197
    Joined: Nov 15 2012 - 10:47am
    Last seen: 1 day 4 hours ago
    Feedback
    randomness