> ## Content Index
> Fetch the complete content index at: https://www.blog.nestict.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Nextcloud White Screen After Update in EasyPanel: Troubleshooting and Fix Guide
- URL: https://www.blog.nestict.com/nextcloud-white-screen-after-update-in-easypanel-troubleshooting-and-fix-guide/
- Published: 2026-08-18T06:19:10.000Z
- Updated: 2026-08-18T06:19:10.000Z
- Author: Nestict Infotech CSR
- Tags: nextcloud, easypanel

A Nextcloud installation that suddenly turns into a **completely blank white screen after an update** can look alarming. In a Docker/EasyPanel environment, however, the problem may not be Nextcloud itself.

In one common case, the Nextcloud application was running perfectly, but its **PostgreSQL database container had stopped**. Nextcloud was therefore unable to resolve or connect to its database, producing a white screen.

This guide explains how to diagnose and fix this type of problem safely.

## The Problem

After updating Nextcloud in EasyPanel, the website may display:

> **White screen / blank page**

Trying to run:

```bash
php occ status
```

may produce an error similar to:

```text
Doctrine\DBAL\Exception:
Failed to connect to the database

SQLSTATE[08006] [7]
could not translate host name
"nestict_icloud-db" to address:
Name or service not known
```

The important part is:

```text
could not translate host name
```

This indicates that Nextcloud cannot resolve the hostname assigned to its database service.

It does **not necessarily mean that the database has been deleted or corrupted**.

---

# What Causes This?

In an EasyPanel/Docker installation, Nextcloud and PostgreSQL normally run as separate containers.

A typical architecture looks like this:

```text
                    Internet
                       │
                       ▼
                 EasyPanel Proxy
                       │
                       ▼
              ┌─────────────────┐
              │    Nextcloud    │
              │    Container    │
              └────────┬────────┘
                       │
                       │ Docker Network
                       ▼
              ┌─────────────────┐
              │   PostgreSQL    │
              │    Container    │
              └────────┬────────┘
                       │
                       ▼
                Persistent Volume
```

Nextcloud doesn't normally connect to PostgreSQL using an IP address.

Instead, it uses the Docker/EasyPanel service name, for example:

```text
nestict_icloud-db
```

If that database container stops, is removed, renamed, or becomes disconnected from the Docker network, Nextcloud can no longer resolve the hostname.

The result can be a white screen.

---

# Step 1: Open the Nextcloud Terminal

In EasyPanel:

**Project → Nextcloud → Nextcloud service → Terminal**

Run:

```bash
cd /var/www/html
```

Then check Nextcloud:

```bash
php occ status
```

If the database is unavailable, you may see:

```text
Failed to connect to the database
```

or:

```text
could not translate host name
```

This is the first major clue.

---

# Step 2: Identify the Database Host

Check the database hostname configured in Nextcloud:

```bash
grep -n "dbhost" config/config.php
```

For example:

```php
'dbhost' => 'nestict_icloud-db',
```

This tells us that Nextcloud expects PostgreSQL to be reachable using:

```text
nestict_icloud-db
```

Do **not** randomly change this value.

First determine whether that service actually exists.

---

# Step 3: Test DNS Resolution

From the Nextcloud container run:

```bash
getent hosts nestict_icloud-db
```

If the database is available, you should receive an IP address.

For example:

```text
172.18.0.5    nestict_icloud-db
```

If you receive nothing, or something similar to:

```text
Name or service not known
```

Nextcloud cannot resolve the database service.

You can also test:

```bash
ping -c 2 nestict_icloud-db
```

A failed hostname lookup strongly suggests a Docker/EasyPanel service or networking problem.

---

# Step 4: Check the Database Container in EasyPanel

Go back to:

**EasyPanel → Your Project**

Locate the PostgreSQL database service.

Check whether it is:

```text
Running
```

or:

```text
Stopped
```

If it is stopped, start it.

Give PostgreSQL a few seconds to initialize.

Then return to the Nextcloud terminal and run:

```bash
php occ status
```

If the database has successfully restarted, Nextcloud should be able to communicate with PostgreSQL again.

---

# Step 5: Restart the Database Container

If PostgreSQL is stopped, restart it from EasyPanel.

After restarting, check the database logs.

Look for messages indicating:

- PostgreSQL started successfully
- database system is ready to accept connections
- out-of-memory errors
- disk-full errors
- permission errors
- corrupted database files
- failed health checks
- unexpected shutdowns

A database that repeatedly stops should **not simply be restarted repeatedly**.

You need to determine why it stopped.

---

# Step 6: Check Nextcloud Again

Once PostgreSQL is running:

```bash
cd /var/www/html
```

Run:

```bash
php occ status
```

A healthy installation should return information such as:

```text
installed: true
version: ...
maintenance: false
```

The exact version will depend on your installation.

---

# Step 7: Check Whether the Update Is Complete

Once database connectivity is restored, run:

```bash
php occ upgrade
```

If an upgrade is pending, Nextcloud should now be able to communicate with PostgreSQL and complete it.

Do **not** repeatedly run the upgrade while the database is unavailable.

Database connectivity must be restored first.

---

# Step 8: Run Nextcloud Repair

After a successful upgrade:

```bash
php occ maintenance:repair
```

Then update the Apache/Nextcloud rewrite configuration:

```bash
php occ maintenance:update:htaccess
```

Finally restart the Nextcloud container from EasyPanel.

---

# Step 9: Check the Nextcloud Log

Nextcloud's main log is normally located at:

```text
data/nextcloud.log
```

Run:

```bash
tail -n 100 data/nextcloud.log
```

Look for errors such as:

```text
SQLSTATE
Doctrine\DBAL
Connection refused
Name or service not known
```

If these errors disappear after restarting PostgreSQL, the database container was almost certainly the cause of the white screen.

---

# Docker-Level Troubleshooting

If you have SSH access to the VPS hosting EasyPanel, you can inspect the containers directly.

Run:

```bash
docker ps
```

For a cleaner output:

```bash
docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Networks}}"
```

You should be able to identify both:

```text
Nextcloud
PostgreSQL
```

Check the Docker networks:

```bash
docker network ls
```

Then inspect the relevant network:

```bash
docker network inspect NETWORK_NAME
```

Both the Nextcloud and PostgreSQL containers should be attached to the appropriate Docker network.

---

# If the Database Hostname Changed

Suppose `config/config.php` contains:

```php
'dbhost' => 'nestict_icloud-db',
```

but EasyPanel now has a database service with a completely different service name.

Do **not** immediately edit the configuration.

First establish why the service name changed.

Changing the hostname incorrectly could make the situation worse.

The correct database hostname must correspond to a service that:

1. Exists
2. Is running
3. Is reachable from Nextcloud
4. Uses the correct PostgreSQL database
5. Is attached to the same Docker network

---

# Don't Delete the Database Volume

This is extremely important.

If Nextcloud suddenly displays a white screen, **do not immediately delete or recreate PostgreSQL with a fresh volume**.

Avoid commands or actions that destroy persistent database storage.

For example, do not casually remove:

```text
PostgreSQL volume
```

or use destructive Docker commands while troubleshooting.

Your Nextcloud files may still be perfectly intact, and your database may simply have been stopped.

---

# Why Restarting PostgreSQL Fixed the Problem

In the reported scenario, the error was:

```text
could not translate host name
"nestict_icloud-db"
```

The Nextcloud container itself was running.

However, the database container was not available.

Once the PostgreSQL container was restarted:

```text
Nextcloud
   │
   │
   ▼
nestict_icloud-db
   │
   ▼
PostgreSQL
   │
   ▼
Database
```

the hostname became available again.

Nextcloud could reconnect to PostgreSQL and the application returned to normal operation.

---

# Preventing the Problem in Future

A database container stopping is more important than the white screen itself.

Check the PostgreSQL logs and VPS resources.

### Check disk space

From the VPS:

```bash
df -h
```

Pay particular attention to:

```text
/
```

and the filesystem containing Docker data.

### Check memory

```bash
free -h
```

Also check running containers:

```bash
docker stats
```

Look for PostgreSQL consuming excessive memory.

### Check container status

```bash
docker ps -a
```

A database container showing:

```text
Exited
```

should be investigated.

### Check PostgreSQL logs

From the VPS:

```bash
docker logs --tail 200 DATABASE_CONTAINER_NAME
```

Replace:

```text
DATABASE_CONTAINER_NAME
```

with the actual PostgreSQL container name.

---

# Quick Recovery Checklist

If Nextcloud suddenly becomes a white screen after an EasyPanel update:

```text
1. Check php occ status
2. Read the database connection error
3. Check dbhost in config.php
4. Test hostname resolution
5. Check PostgreSQL service in EasyPanel
6. Start/restart PostgreSQL if stopped
7. Check PostgreSQL logs
8. Run php occ status again
9. Run php occ upgrade if necessary
10. Run php occ maintenance:repair
11. Restart Nextcloud
12. Check nextcloud.log
```

### The key lesson

A **Nextcloud white screen does not automatically mean the Nextcloud update broke Nextcloud**.

In a Docker/EasyPanel deployment, always check the dependency chain:

```text
Browser
   ↓
Reverse Proxy
   ↓
Nextcloud
   ↓
Docker Network
   ↓
PostgreSQL
   ↓
Persistent Database Volume
```

If PostgreSQL disappears from that chain, Nextcloud may simply have nothing to talk to. Restoring the database service can bring the entire installation back without reinstalling Nextcloud or touching user files.