My final panic!!!!

It is the day of submission for this assignment, so I decide to check my staff and OPAC interface one more time.

The staff interface does not work. The error message says it is taking too long to load. I instantly panic, misremembering having tested this on work computer (I had only tested the OPAC, not the staff interface, for some reason).

I decide to ask my husband to check AWS, as this is also not running correctly on my work computer. He says that both the OPAC and staff interface still work as normal. I don't understand, but am less panicked. He suggested that, since the staff interface is on a non-default port (8080, instead of HTTP's usual 80), that it could just be my work's proxy server refusing connections to ports that are not 80. I therefore try check an unrelated site running on a non-default port, and it too does not work. This seems to confirm the problem is at my end.

I try to access through webproxy.net, but this site is blocked by my work. If this were to be implemented through my work, we would need to consider whether this would be an issue on the internal servers, or, if we decided to run on external servers, whether we could perhaps have our 8080 site allowed. Alternatively, after briefly researching the Koha Community wiki (and looking at the Koha pre-web configuration), it looks like we could run the both the staff interface and the OPAC on port 80 on the same server.