Reverting this until we have an SSL cert with www.neatf2p.com as the common name, that is issued by www.neatf2p.com. Or at least the first one.
With this change in place that we are reverting, the webclient DOES load without accepting a privacy warning. Unfortunately though, with the existing websocket cert, we get certificate_unknown in the terminal when a player tries to log in, and "Sorry! Unable to connect" in the webclient.
Reverts aldrichdev/neatf2p-nextjs#126
Reverting this until we have an SSL cert with www.neatf2p.com as the common name, that is issued by www.neatf2p.com. Or at least the first one.
With this change in place that we are reverting, the webclient DOES load without accepting a privacy warning. Unfortunately though, with the existing websocket cert, we get
certificate_unknown
in the terminal when a player tries to log in, and "Sorry! Unable to connect" in the webclient.