Thanks! Got the reverse proxy working. Now the secure part of connection is taken care by the proxy, even if my app itself is non-secure. For information to other folks, here's what I did: Added following in the snap/snapcraft.yaml file: parts: [...] configs: source: ./configs plugin: dump organize: 'package-assets/*': package-assets/${SNAPCRAFT_PROJECT_NAME}/ slots: package-assets: interface: content content: package-assets source: read: - $SNAP/package-assets/${SNAPCRAFT_PROJECT_NAME} And created file configs/package-assets/my-app.package-manifest.json { "version": "0.0.0", "id": "my-app", "services": { "proxyMapping": [ { "name": "my-app.ws", "url": "/my-app", "binding": ":8080", "restricted": [ ] } ] } } So, now I can open secure WebSocket connection to 'wss://my-host/my-app' which is redirected to my-app bound to port 8080 in this case. However, I can still open non-secure WebSocket connection from external host directly to my app 'ws://my-host:8080'. How do I prevent that? Some firewall settings needed?
... View more
