Activity for Pantu

  • Pantu Pantu modified a comment on discussion Help

    Hey Emmanuel, I had the same problem. The fix is to add: underscores_in_headers on; To your nginx config. See here: https://sourceforge.net/p/jobscheduler/discussion/486122/thread/c739bb2e/

  • Pantu Pantu posted a comment on discussion Help

    Hey Emmanuel, I had the same problem. The fix is to add: underscores_in_headers on; To your nginx config. See here: https://sourceforge.net/p/jobscheduler/discussion/486122/thread/c739bb2e/

  • Pantu Pantu posted a comment on discussion Help

    @Andreas. Thanks for the explanation. I might have gotten something wrong. The classic JOC interface seems to be available over http on port 4444 and port 40444. Didnt understand why it is accessable via both. Classic JOC 4444 port="" and ip_address="" refer to the classic interface. ip_address lets me actually bind it to a specific IP address and port to the desired port. <allowed_host> works for the service which is available through the above two config switches Classic JOC 40444 http_port opens...

  • Pantu Pantu modified a comment on discussion Help

    Hi everybody, when using the legacy JOC, it is accessable from everywhere on port 40444. However, I only want it to listen on 127.0.0.1:40444 as I will use a reverse proxy anyway. How can I change the web listening address for the legacy JOC? Thanks for the help Edit scheduler.xml <?xml version="1.0" encoding="iso-8859-1" standalone="no"?> <?xml-stylesheet type="text/xsl" href="scheduler_documentation.xsl" ?> <spooler> <config mail_xslt_stylesheet="config/scheduler_mail.xsl" http_port="40444" port="4444"...

  • Pantu Pantu posted a comment on discussion Help

    @Clement Thanks for the answer. Unfortunately I don't have any graphical tools available. Only thing I got is vi. Mind pasting some code snippet from scheduler.xml?

  • Pantu Pantu modified a comment on discussion Help

    Hi everybody, when using the legacy JOC, it is accessable from everywhere on port 40444. However, I only want it to listen on 127.0.0.1:40444 as I will use a reverse proxy anyway. How can I change the web listening address for the legacy JOC? Thanks for the help Edit scheduler.xml <?xml version="1.0" encoding="iso-8859-1" standalone="no"?> <?xml-stylesheet type="text/xsl" href="scheduler_documentation.xsl" ?> <spooler> <config mail_xslt_stylesheet="config/scheduler_mail.xsl" http_port="40444" port="4444"...

  • Pantu Pantu modified a comment on discussion Help

    Hi everybody, when using the legacy JOC, it is accessable from everywhere on port 40444. However, I only want it to listen on 127.0.0.1:40444 as I will use a reverse proxy anyway. How can I change the web listening address for the legacy JOC? Thanks for the help Edit scheduler.xml <?xml version="1.0" encoding="iso-8859-1" standalone="no"?> <?xml-stylesheet type="text/xsl" href="scheduler_documentation.xsl" ?> <spooler> <config mail_xslt_stylesheet="config/scheduler_mail.xsl" http_port="40444" port="4444"...

  • Pantu Pantu posted a comment on discussion Help

    Hi everybody, when using the legacy JOC, it is accessable from everywhere on port 40444. However, I only want it to listen on 127.0.0.1:40444 as I will use a reverse proxy anyway. How can I change the web listening address for the legacy JOC? Thanks for the help

  • Pantu Pantu posted a comment on discussion Help

    @Andreas, First of all, yes its a company policy and secondly simply by having multiple domains/sub-domains pointing to the server and I want each to serve the right service.

  • Pantu Pantu posted a comment on discussion Help

    @Daniel, could you please paste your nginx config. I tried mine with underscores_in_headers turned off, however I still have the same problem.

  • Pantu Pantu modified a comment on discussion Help

    Hi Team, I am trying to setup the latest version for the newly designed JOC cockpit. In order to use SSL and port 443 I added an Nginx reverse proxy in front of it. However, using the nginx reverse proxy results in a Session Timeout during login. Without the reverse proxy everything works fine. The Error is: Session Timeout! Your session has expired and a login is required The logs leave me with only this: 2017-05-03 10:16:14,228 INFO qtp2121744517-18 c.s.j.c.JocCockpitProperties - Resolved path...

  • Pantu Pantu modified a comment on discussion Help

    Hi Team, I am trying to setup the latest version for the newly designed JOC cockpit. In order to use SSL and port 443 I added an Nginx reverse proxy in front of it. However, using the nginx reverse proxy results in a Session Timeout during login. Without the reverse proxy everything works fine. The Error is: Session Timeout! Your session has expired and a login is required The logs leave me with only this: 2017-05-03 10:16:14,228 INFO qtp2121744517-18 c.s.j.c.JocCockpitProperties - Resolved path...

  • Pantu Pantu modified a comment on discussion Help

    Hi Team, I am trying to setup the latest version for the newly designed JOC cockpit. In order to use SSL and port 443 I added an Nginx reverse proxy in front of it. However, using the nginx reverse proxy results in a Session Timeout during login. Without the reverse proxy everything works fine. The logs leave me with only this: 2017-05-03 10:16:14,228 INFO qtp2121744517-18 c.s.j.c.JocCockpitProperties - Resolved path of log4j.properties = /home/bi/joc.1.11.1/scheduler/jetty/resources/joc/log4j.properties...

  • Pantu Pantu modified a comment on discussion Help

    Hi Team, I am trying to setup the latest version for the newly designed JOC cockpit. In order to use SSL and port 443 I added an Nginx reverse proxy in front of it. However, using the nginx reverse proxy results in a Session Timeout during login. Without the reverse proxy everything works fine. The logs leave me with only this: 2017-05-03 10:16:14,228 INFO qtp2121744517-18 c.s.j.c.JocCockpitProperties - Resolved path of log4j.properties = /home/bi/joc.1.11.1/scheduler/jetty/resources/joc/log4j.properties...

  • Pantu Pantu modified a comment on discussion Help

    Hi Team, I am trying to setup the latest version for the newly designed JOC cockpit. In order to use SSL and port 443 I added an Nginx reverse proxy in front of it. However, using the nginx reverse proxy results in a Session Timeout during login. Without the reverse proxy everything works fine. The logs leave me with only this: 2017-05-03 10:16:14,228 INFO qtp2121744517-18 c.s.j.c.JocCockpitProperties - Resolved path of log4j.properties = /home/bi/joc.1.11.1/scheduler/jetty/resources/joc/log4j.properties...

  • Pantu Pantu posted a comment on discussion Help

    Hi Team, I am trying to setup the latest version for the newly designed JOC cockpit. In order to use SSL and port 443 I added an Nginx reverse proxy in front of it. However, using the nginx reverse proxy results in a Session Timeout during login. Without the reverse proxy everything works fine. The logs leave me with only this: 2017-05-03 10:16:14,228 INFO qtp2121744517-18 c.s.j.c.JocCockpitProperties - Resolved path of log4j.properties = /home/bi/joc.1.11.1/scheduler/jetty/resources/joc/log4j.properties...

1
MongoDB Logo MongoDB