You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At first I could replicate the issue in my local development environment. Then I've started the Gatekeeper in the debugger, trying to see what causes the issue in GatekeeperMain. Everything looked allright, and when I checked 8448/api/, now the correct endpoints were showing. The endpoints did not change back after this on my local machine.
When I restarted the arrowhead VM, the issue is still present there. My best guess so far, that this is some kind of caching issue with Swagger, the gatekeeper core system is the only one where 2 webservers are started from the same main method.
Today I've noticed that both http://arrowhead.tmit.bme.hu:8346/api/ and http://arrowhead.tmit.bme.hu:8348/api/ show the same endpoints, but the latter should show different endpoints. The actual webserver has the correct endpoints, this is only a Swagger issue. http://arrowhead2.tmit.bme.hu:8348/api/ shows the correct endpoints.
At first I could replicate the issue in my local development environment. Then I've started the Gatekeeper in the debugger, trying to see what causes the issue in GatekeeperMain. Everything looked allright, and when I checked 8448/api/, now the correct endpoints were showing. The endpoints did not change back after this on my local machine.
When I restarted the arrowhead VM, the issue is still present there. My best guess so far, that this is some kind of caching issue with Swagger, the gatekeeper core system is the only one where 2 webservers are started from the same main method.