Outline-client: [Question] [Windows] Cannot connect behind proxy and due to blocked ports

[evil-shrike]

Hi.

I'm trying to run Outline Windows client behind our corporate proxy. It doesn't work. It seems that Outline itself isn't supporting going through a proxy. And it has no any settings for customizing port(s). I even cannot ask our admin for opening some ports for me as it's unclear which ones.

So in the whole it seems unusable now for using from companies. And honestly I can't any advantages against other "single-script" VPNs based on OpenVPN or L2TP/IPSec and so on. But idea is great.

So let me ask about any plans for the mentioned scenario - connecting behind corporate proxies - will it work someday?
Thanks.

[bemasc]

Thanks for your feedback.

Each access key has a fixed port, so you could ask your administrator to open the port corresponding to your personal access key.

Could you give an example of a proxy or VPN client that has good compatibility with your corporate proxy?

[evil-shrike]

As I can remember OpenVPN worked fine with config like that:

dev tun
proto tcp-client
remote 1.2.3.4
port 8443
http-proxy proxy.example.org 8000
client
tls-client
ns-cert-type server

Also usually 389 (Windows RDP) port is opened on firewalls and if vpn software can go through it it won't be required for any additional proxy configuration. I used to setup tunneling via SSH channel to dropbear on my router.

[navidlukas]

I have successfully changed ports to 443 and other, from here, change the random port to whatever you want, reboot, then re-add the key.

nano /root/shadowbox/persisted-state/shadowbox_config.json

[evil-shrike]

@navidlukas cool, thanks!

[slopedelpalacio]

Thank you @navidlukas! Is it possible to use the same port (443) with more than one user? I am getting a "access key not valid" error...

[navidlukas]

@slopedelpalacio Yes, I am sharing one key using one port with several people concurrently without any problems. "access key not valid" I think the port 443 is being used by another application. It worked fine for me on a minimal VPS. After you make the port change, reboot, then share and re-add the key link.

[slopedelpalacio]

@navidlukas thanks! :)

[immartian]

Is it possible to show such an error explicitly? So at least some users can negotiate this with IT staff to open some ports related.