I've got a problem that may be more of a networking issue than a SuperContainer problem, but I haven't bee able to resolve it yet and figured that I might be able to find the answer here.

Our website server (IIS) has an 'internal' and external IP addresses setup which has been running OK for a few years now. The internal IP is mainly for RDC purposes. The server is not part of our internal domain, so I had to setup SuperContainer on the website server itself, since it won't have access to any storage. I setup SuperContainer as a 'standalone server' type on this webserver. A certain webpage contains links that point to files that S.C. will be handling and displaying. A typical link looks like such -

http://www.website.com:8020/SuperContainer/RawData/78993?username=UN&password=PW

Clicking on the link(s) works just fine from an internal perspective, meaning any computer inside our company and on 'this side' of the firewall. But once I try from home or from 'the outside', I get a timeout error each time.

Any ideas?

This is definitely a networking issue. You will need to use an external IP address when accessing the server from outside of your network. Also make sure you have any ports forwarded that you need to forward, an that you have 8020 open in your firewall.

This is definitely a networking issue. You will need to use an external IP address when accessing the server from outside of your network. Also make sure you have any ports forwarded that you need to forward, an that you have 8020 open in your firewall.

Just for the sake of reference, I forgot to open the port (8020) on the website's firewall, which was causing the problem. Silly mistake that I made.