Enable SSL on the darq.chat domain
Currrently the darq.chat domain uses a HTTP connection which allows for potential MITM attacks.
In order to enable this easily on AWS we first need to proxy the server behind nginx.
As of 2024-05-14 a change has been implemented to enforce access token expiry. If you see higher numbers of HTTP 401 responses, please check tokens that may have expired. For more details, including how to mitigate disruption, please check our docs guide on Expired Access Tokens. If you have a support contract, you may open a support ticket for additional assistance.
Currrently the darq.chat domain uses a HTTP connection which allows for potential MITM attacks.
In order to enable this easily on AWS we first need to proxy the server behind nginx.