[SOLVED] Appwrite problems 1.2.1

Getting 0 Network request failed, one day after update to 1.2.1. Also in api getting Failed Host Lookup

👩‍⚕️ Running Appwrite Doctor for version 1.2.1 ...

Checking for production best practices... 🟢 Hostname has a public suffix (xxx.xxx) 🟢 CNAME target has a public suffix (xxx.xxx) 🟢 Using a unique secret key for encryption 🔴 App environment is set for development 🔴 Abuse protection is disabled 🟢 Console access limits are enabled 🟢 HTTPS force option is enabled 🔴 Logging adapter is disabled

Checking connectivity... Database............connected 👍 Queue...............connected 👍 Cache...............connected 👍 SMTP................connected 👍 StatsD..............connected 👍 InfluxDB............connected 👍

Checking volumes... 🟢 Uploads Volume is readable 🟢 Uploads Volume is writeable 🟢 Cache Volume is readable 🟢 Cache Volume is writeable 🟢 Config Volume is readable 🟢 Config Volume is writeable 🟢 Certs Volume is readable 🟢 Certs Volume is writeable

Checking disk space usage... 🟢 Uploads Volume has 9.99GB free space (61.32% used) 🟢 Cache Volume has 9.99GB free space (61.32% used) 🟢 Config Volume has 9.99GB free space (61.32% used) 🟢 Certs Volume has 9.99GB free space (61.32% used)

TL;DR

Title: [SOLVED] Appwrite problems 1.2.1 Summary: The issue was resolved. The problem was with caching and a temporarily offline domain. The user was getting a network request failed error and failed host lookup. The Appwrite doctor was run and showed that all components were connected and volumes were readable and writable. Disk space usage was also checked and had sufficient free space. Solution: The user discovered that the issue was caused by a temporarily offline domain. Once the domain was back online, the issue was resolved.

Hi there 👋 , let me look into this and be back!

Can you tell me what your endpoint is set to?

What url are you accessing Appwrite at? Do you have a self signed certificate? Whats in the browser console logs?

Hello, I found the issue. Domain was temporarily offline. (I have something like app.mything.dev).

However, everything was hard cached, and I could navigate in the console to all the elements but when I requested some update to the documents I got that error with 0. but in reality the whole domain was unliked.

I now realise that the caching console is a bit of problem when the domain got bust. The overview was also showing data, but cached data.

In other words this is solved for me, with the note of console weird behaviour in terms of caching.