How to create static access keys for ShadowSocks over WebSocket servers?

[emohandesi]

Is there a way to create a static key for ShadowSocks over WebSocket servers? AWS or other key storage servers are blocked in Iran right now, and that has added an additional point of failure for the users to connect to the VPN servers.

[ohnorobo]

No, unfortunately websockets is only available with advanced config. You could try serving the advanced config yaml file from the same network. That way at least they'll likely both be accessible together or not.

[emohandesi]

All resources inside Iran are blocked from outside Iran at the moment. Iran's internet is almost an intranet right now. I had a couple of servers in Iran, but I do not have access to them anymore, so storing the key somewhere close to the users is not an option for now.
By the way, I believe the Outline Add VPN access key box should also have the ability to accept JSON or YAML plain text keys, as well, in addition to ss and ssconf keys it currently accepts. This way, we can get around this issue in the future.

[emohandesi]

One way to get around this issue and remove the dependence on a 3rd party for hosting the dynamic access key is to set up an HTTPS server on the same server that hosts the VPN and provide the dynamic access key through that.
It means you need to have a domain name and point it to the IP of the VPN server because getting an SSL certificate for the IP of your server for setting up an HTTPS server requires organizational ownership of the IP, which you do not have.
Thanks to Junyi for suggesting this workaround of hosting the dynamic access key on the same VPN server.