Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Hi, I’m getting this error when updating our certificate at parrity.com
Domain: parrity.com Type: unauthorized Detail: Invalid response from https://parrity.com/.well-known/acme-challenge/YGTIOs7qXPpAqw_mtMZuXjKdgZvyipwDNvQbK6vKk8Q [46.101.240.67]: “<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx/1.19.10</c”
To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address.
I checked our domain A records, and they do point to the I.P 46.101.240.67, a staging domain - next.parrity.com, which is not part of the certificate and is not active atm { 404 error }.
Could this be the issue?
I just changed the records to the original I.P hoping to fix the issue.
Unfortunately, my co-founder CTO is based in Ukraine and I need to fix this on my own. Idk why they point to the staging server. I’m guessing it could be connected to our automated GitLab CD/CI
Thanks in advance.
Edward Sitarski
1fd6b9d2a2b94ee4b3e8ee6d5e2587
Traceurity
fadecomic
Mollie Semmes
Will Walters
f4df2e98b9c74f7eb7f6a0629cf1c4
erel
fingers
fingers