Chris Guida

Would be cool to have an OS feature that allows any username in containers, that way we don't need to adapt every upstream codebase to use `start9`

Not sure if changing the outer port to 443 works better or not. Now I just get redirected to the embassy login page. Same result in `curl`.

For the record, I also can't get this interface to work over Tor either, but I'm not sure if that's because of the current Tor ddos attack.

Are you suggesting that i turn ssl to false?

i suppose i could also use the system cert

So what's the fix?

The rest api requires https, obviously, otherwise a middleman can steal the macaroon

Tried it with ssl: false in the manifest and the output is different, but still not working. guessing you were saying this ``` % curl -k https://kyikw2zkhwye3zpenl35bizk7vowsn4mxs3hyxxgjijosjhriru2iwid.local:3001 curl: (35) error:1400410B:SSL...

Ok at least i figured out Tor. Forgot to put `https://` when connecting over Tor xD ``` % curl -k --socks5-hostname localhost:9050 https://kyikw2zkhwye3zpenl35bizk7vowsn4mxs3hyxxgjijosjhriru2iwid.onion:3001 Error Cannot GET / ```

I'm just trying to ascertain whether accessing https services on ports other than 443/80 is possible at all. Currently the plugin is generating its own cert, but this is not...