Cannot load web portal with custom port number

Legacy Uncategorised
1

I have changed the port number of my octopus portal due to an issue I was having running the server in interactive mode.

The server now runs, but I cannot run the web portal. If I navigate to http://localhost:81/octopus, the page does not load at all. Nothing in the windows event log to give me a clue as to why.

To clarify, I cannot access the portal either while the service is running, or when running the interactive server, both return “Oops! Google Chrome could not connect to localhost:81” .

Not sure if I am missing something here.

2

Hi Andrew,

I’m giving up on the embedded web server approach - the next build will use IIS. Hopefully that will eliminate these issues :slight_smile:

Paul

3

Awesome - well third time lucky hey? Looking forward to it.

4

This build should fix the problem: