Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 216
    • Issues 216
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #532

Closed
Open
Created Apr 15, 2021 by Nicolas E@nec

Stork web gui failing on port 80, but working when specify 8080.

Hello, and thank you for all this work and doc. I'm using Kea+Stork since 1.9.2 and it's working fine.

Recently, I upgraded to 1.9.6 and though I went through the Stork agent registering quite seemlessly, I'm noticing that the Stork web gui, served by nginx, is now only operational through http://mycompany-kea-nginx-server.com:8080 when it was previously OK through http://mycompany-kea-nginx-server.com

This is not a big deal, but I didn't change the nginx setup when upgrading.

When using the (ommitted by default) port 80 URL, I'm reaching the login page, but I'm seeing lots of errors in the browser console, and the kea version cannot be displayed ("unknown"). Though, I can enter in the web gui, I see the usual menus, but every local data is missing.

I see no error in the logs files of nginx neither stork server or agent.

The only errors I see are from the browser dev console : [1].

For a nginx config file, I'm using the file provided in the stork example directory, coming with the Debian 10 package.

I wanted to know what has changed around this subject and if there is a way to recover the simplest previous URL?

Thank you

Nicolas

[1] The browser errors :

problem with getting settings 
Object { headers: {…}, status: 400, statusText: "Bad Request", url: "http://cti-dhcp-prd01.sitpi.lan/api/settings", ok: false, name: "HttpErrorResponse", message: "Http failure response for http://cti-dhcp-prd01.sitpi.lan/api/settings: 400 Bad Request", error: {…} }
main-es2015.5726ecb1650428b6badd.js:1:2678830
ERROR 
Object { headers: {…}, status: 400, statusText: "Bad Request", url: "http://cti-dhcp-prd01.sitpi.lan/api/version", ok: false, name: "HttpErrorResponse", message: "Http failure response for http://cti-dhcp-prd01.sitpi.lan/api/version: 400 Bad Request", error: {…} }
main-es2015.5726ecb1650428b6badd.js:1:2036800
GEThttp://cti-dhcp-prd01.sitpi.lan/assets/stork-logo-big.png
[HTTP/1.1 200 OK 74ms]

GEThttp://cti-dhcp-prd01.sitpi.lan/open-sans-v15-latin-regular.ec806460121999bcfb12.woff2
[HTTP/1.1 200 OK 164ms]

GEThttps://fonts.gstatic.com/s/mansalva/v4/aWB4m0aacbtDfvq5NKliKY8.woff2
[HTTP/1.1 200 Connection established 380ms]

GEThttp://cti-dhcp-prd01.sitpi.lan/primeicons.04701ca33ce96d325419.ttf
[HTTP/1.1 200 OK 274ms]

XHRGEThttp://cti-dhcp-prd01.sitpi.lan/api/version
[HTTP/1.1 400 Bad Request 84ms]

XHRGEThttp://cti-dhcp-prd01.sitpi.lan/api/apps-stats
[HTTP/1.1 400 Bad Request 81ms]

Object { headers: {…}, status: 400, statusText: "Bad Request", url: "http://cti-dhcp-prd01.sitpi.lan/api/version", ok: false, name: "HttpErrorResponse", message: "Http failure response for http://cti-dhcp-prd01.sitpi.lan/api/version: 400 Bad Request", error: {…} }
Assignee
Assign to
Time tracking