etheron

Unable to Log In to Your VPS or Forgot Your Password? Here’s How to Reset It!

1. Log in to your VPS panel.

2. Click on **Manage** for the desired server.

3. Go to **Options**.

4. Scroll down and click on **Reset Password**.

5. You’ll be asked to select the user. Choose the desired user (this is usually **root**) and click on **Reset**.

6. Log in to the email account associated with your VPS panel. Look for an email titled: **Your New Server Password**.

7. This email contains your new password!
If you encounter any issues, feel free to reach out via Discord or create a support ticket through this link.

Learn how to reset the password of my VPS with clear step-by-step instructions.

How do I reset the password of my VPS?

Here’s How to Grant a User Access to Your VPS.

Granting access allows the other person to view all data on your VPS. Be cautious about whom you share access with!

**For the User Receiving Access.**

1. Log in to the VPS panel.

2. Click on your name in the top-right corner.

3. Click on **Account.**

4. Click **Sharing.**

5. Click on **Generate Token.**

6. Copy the generated token and send it to the VPS owner.

**For the VPS owner.**

1. Log in to the VPS panel.

2. Click **Manage** on the desired server.

3. Navigate to **Sharing.**

4. Paste the **token** from the person requesting access.

5. Click **Grant Access.**

6. Choose the permissions for the user on your VPS.

If you encounter any issues, feel free to reach out via Discord or create a support ticket through this link.

Granting access allows the other person to view all data on your VPS. Be cautious about whom you share access with!

How can I grant a User access to my VPS?

ModSecurity is a security module for web servers that automatically blocks suspicious HTTP requests. This protects your website against attacks, but can sometimes also block legitimate requests (so-called 'false positives'). This then leads to a **403 Forbidden error message** when you or your visitors try to access certain pages.

In this article you'll learn how to:
- Identify which ModSecurity rule is causing a block
- Disable specific rules per domain
- Completely deactivate ModSecurity for a domain (if necessary)

## What do you need?

- Access to the [web panel](http://web1.ping64.net:2222) as a user of the relevant domain
- DirectAdmin access at VPS level
- Basic knowledge of reading log files

---

## Step 1: Identify the blocked rule

Before you can adjust a rule, you first need to know which rule is causing the block.

### 1.1 Open the error logs

1. Log in to the [web panel](http://web1.ping64.net:2222) with the credentials of the relevant domain
2. Navigate to **System Info & Files**
3. Click on **Site Summary / Statistics / Logs**
4. Open the **Error Log**

### 1.2 Search for the ModSecurity notification

Scroll through the log file and look for lines that start with `ModSecurity: Access denied`. A typical error message looks like this:

```
[Fri Nov 20 17:00:50.493215 2020] [:error] [pid 20195:tid 140060137608960] 
[client 1.2.3.4:50882] ModSecurity: Access denied with code 403 (phase 2). 
Match of "rx ^(\\d*|uploads\\/.*\\.(jpeg|jpg|gif|png|bmp))$" against "ARGS_GET:img" required. 
[file "/usr/local/cwaf/rules/29_Apps_WPPlugin.conf"] [line "624"] [id "222050"] 
[rev "4"] [msg "COMODO WAF: Directory traversal vulnerability..."] 
[severity "CRITICAL"] [hostname "www.example.com"] [uri "/wp-admin/admin-ajax.php"]
```

### 1.3 Note the rule ID

The most important part is the **rule ID**, in the above example: `[id "222050"]`

Note this number – you'll need it in the next step.

---

## Step 2: Disable the rule

Now that you know which rule is causing the block, you can specifically disable it for the relevant domain.

1. In DirectAdmin, go to **Account Manager** (hover your mouse over the menu item)
2. Click on **Domain Setup**
3. Select the domain for which you want to disable the rule
4. Click on the **ModSecurity** button (at the bottom or top right in the domain settings)
5. Enter the rule ID you found in step 1 (for example `222050`)
6. Click on **Disable Rule**

The rule is now disabled for this specific domain. Other domains on the same server will still be protected by this rule.

---

## Completely disabling ModSecurity (not recommended)

If you're experiencing many problems with ModSecurity and want to temporarily disable all security checks for a domain, you can do this as follows:

1. Follow the same steps as above up to the **ModSecurity** screen
2. Find the **SecRuleEngine** setting
3. Set this to **Off**
4. Save the change

⚠️ **Warning**: This disables all ModSecurity protection for the domain. Only use this temporarily for testing, not as a permanent solution.

---

## Common problems

### I don't see any ModSecurity notifications in my error log

- Check if you're looking at the correct date/time when the block occurred
- Some blocks may also be in other log files; try viewing the **Apache Error Log** as well
- If the logs are empty, ModSecurity may not be active for this domain

### The error message persists after disabling the rule

- Clear your browser cache and try again
- Check if you've selected the correct domain
- It may take a few seconds before the change becomes active – reload the page after 30 seconds

### Which rules can I safely disable?

This depends heavily on your situation. General guidelines:

- Only disable rules that you're certain are causing a false positive
- Document which rules you disable and why
- Consider fixing the underlying cause instead of disabling the rule (for example: update your WordPress plugins if the rule detects a known vulnerability)

---

## Related information

- VPS access: [VPS panel](https://cloud.ping64.net)
- DirectAdmin login: [Web panel](http://web1.ping64.net:2222)

Need help? Contact us via support.etheron.nl

Adjusting ModSecurity Rules in DirectAdmin

Are you experiencing problems defeating the Ender Dragon due to server lag? The combination of low TPS (ticks per second), high latency, and the resource-intensive Ender Dragon fight can make the battle impossible or unfair. This article provides concrete solutions for both acute and structural performance problems.

## Diagnosis: Server lag or client lag?

Before you start optimizing, first determine where the problem lies:

### Server-side lag (this article focuses on this):
- TPS (ticks per second) below 20 (check with `/tps` or `/spark tps`)
- All players experience lag simultaneously
- Mobs move jerkily for everyone
- Blocks break with delay for all players

### Client-side lag:
- Low FPS for individual players
- Other players experience no problems
- Only visual stuttering, no gameplay delay

## Immediate temporary solutions

### Step 1. Restart the server before the Dragon fight

A fresh server start has no memory leaks or accumulated entities. Access via the game panel at https://game.ping64.net → select your server → click "Restart".

### Step 2. Pre-load the End chunks

Teleport to the End and let the chunks load before players arrive:

```
/execute in minecraft:the_end run tp @s 0 64 0
```

Walk a circle of approximately 200 blocks around the spawn platform to force chunks.

### Step 3. Remove unnecessary entities in the End

```
/execute in minecraft:the_end run kill @e[type=!player,type=!ender_dragon,type=!end_crystal]
```

## Structural optimizations

### 1. Lower view distance

Edit the `server.properties` file via the File Manager in the game panel:

```
view-distance=6
simulation-distance=4
```

- `view-distance`: How far players can see chunks (default 10)
- `simulation-distance`: How far mobs/redstone are active (default 10)

**For Dragon fight minimum:**
- view-distance: 6-8
- simulation-distance: 4-6

### 2. Use Paper or Purpur server software

Paper and Purpur are optimized Spigot forks with better performance.

**Advantages:**
- Better entity tracking
- Async chunk loading
- Configurable mob AI optimizations

### 3. Optimize End dimension specifically

If you're using Paper or Purpur, edit `config/paper-world-defaults.yml`:

```yaml
entities:
  behavior:
    ender-dragons-death-always-places-dragon-egg: true
  spawning:
    all-chunks-are-slime-chunks: false
    alt-item-despawn-rate:
      enabled: true
    per-player-mob-spawns: true
    
chunks:
  auto-save-interval: 300  # Increase for less disk I/O during fight
  delay-chunk-unloads-by: 10s
  
environment:
  treasure-maps:
    enabled: false  # Reduces chunk loading
```

### 4. Reduce mob AI complexity

Edit `bukkit.yml`:

```yaml
ticks-per:
  monster-spawns: 4  # Increase from 1 to 4
  animal-spawns: 400
  water-spawns: 400
  water-ambient-spawns: 400
  ambient-spawns: 400
```

## Minecraft version specific problems

### Versions 1.19 and higher

Versions from 1.19 onwards have significantly higher resource requirements due to:
- Chat signing system
- Improved entity collision detection
- Warden AI (even though it's not in the End)

**Recommendation:** Consider downgrading to 1.18.2 or upgrading to 1.20.4 or higher (contains optimizations).

### Versions 1.20.5 and higher: Dragon fight bug

There is a known bug where the Dragon can get stuck in perching state.

**Workaround:**

```
/data merge entity @e[type=ender_dragon,limit=1] {DragonPhase:0}
```

This resets the Dragon AI to "circling" phase.

## Check server resources

### RAM usage

The End fight requires at least **2GB free RAM** during the battle.

**Check RAM via:**
- Game panel dashboard
- In-game: `/spark heapsummary`

**Too little RAM?**
- Upgrade your package via https://mijn.etheron.nl
- Or: Lower `simulation-distance` further

### CPU bottleneck

The Dragon AI is single-threaded and CPU-intensive.

**Check with Spark profiler:**

1. Install the Spark plugin
2. Start profiling: `/spark profiler start`
3. Fight Dragon for 2-3 minutes
4. Stop profiling: `/spark profiler stop`
5. Analyze the URL: Look at "Tick" percentage of `EnderDragon.aiStep()`

**If Dragon uses >30% of tick time:**
- Consider lowering Dragon health with a datapack
- Or use a plugin for simplified Dragon AI

## Common problems

### "TPS is 20 but Dragon still responds slowly"

This is likely an **MSPT (milliseconds per tick)** problem:
- Check `/spark tps` → look at MSPT value
- If MSPT >45ms: Ticks are being "skipped" internally
- **Solution:** Follow structural optimizations above

### "Server crashes during Dragon fight"

Crash logs can be found in the game panel under the logs section.

Common causes:

1. **OutOfMemoryError**: Too little RAM → upgrade or optimize
2. **Watchdog crash**: Tick took >60 seconds → lower simulation-distance drastically
3. **Plugin conflict**: Disable plugins and test incrementally

### "Dragon doesn't regenerate via End Crystals"

Not a lag problem, but a game mechanic bug in some versions.

**Fix:**

```
/data merge entity @e[type=end_crystal,limit=1,sort=nearest] {BeamTarget:{X:0,Y:128,Z:0}}
```

Ensures crystals beam to Dragon portal pillar.

## Monitoring during fight

Use these commands to follow live performance:

```
/spark tps  # Check every 30 seconds
/spark tickmonitoringstart  # Warns of long ticks
/minecraft:debug start  # Vanilla profiling (stop after 10 sec)
```

**Target values:**
- TPS: 19-20
- MSPT: <45ms
- RAM usage: <80% of total

## Preventive measures

### Pre-fight checklist:

1. Server restart
2. `/kill @e[type=item]` (remove dropped items)
3. Ensure <15 players in End simultaneously
4. Disable non-essential plugins temporarily

### Post-fight cleanup:

```
/execute in minecraft:the_end run kill @e[type=item]
/execute in minecraft:the_end run kill @e[type=experience_orb]
```

### Scheduled restarts:

Set daily restarts at 4:00 AM via the game panel to prevent memory leaks.

## Final note

If **no optimization helps** and your server continues to lag during Dragon fights, contact Etheron support via https://mijn.etheron.nl with:
- Your server package details
- Spark profiler URL from during fight
- Number of concurrent players during fight
- Minecraft version and server software

They may be able to apply backend optimizations or discuss hardware upgrade options.

---
Need help? Contact us via support.etheron.nl

Ender Dragon unbeatable due to server lag

In this article, we explain how to install Dokploy on your Etheron VPS using the one-click app in the VPS panel.

Dokploy is a self-hosted Platform-as-a-Service (PaaS). You can use it to manage applications, databases, and Docker containers from your own VPS.

> **Note:** Are you installing Dokploy on a new or rebuilt VPS? Existing data on the VPS may be removed. Make a backup first if the VPS already contains important files.

## What do you need?

- An Etheron Hosting VPS
- Access to the VPS panel via [cloud.ping64.net](https://cloud.ping64.net/)
- An SSH key, if you want to use one

## Installing Dokploy

1. Log in to [cloud.ping64.net](https://cloud.ping64.net/).

2. Open the VPS you want to install and click **Manage**.

3. Start the installation or rebuild through **Server Setup...**.

Give your VPS a recognizable name, for example `Dokploy VPS`. You can leave the hostname empty if you do not need one.

![Set the VPS name](https://support.ping64.nl/logos/image-1780758923271-744670881.png)

4. Choose the correct timezone, for example **Europe/Amsterdam**.

5. Go to **Operating System** and choose **One-Click Apps**.

Then select **Ubuntu Server + Dokploy 24.04 LTS**.

![Choose Dokploy under One-Click Apps](https://support.ping64.nl/logos/image-1780758991954-704310115.png)

6. Check the extra options, such as **Swap Space**, IPv6, and SSH keys.

For Dokploy, swap is useful as an extra safety net when RAM usage temporarily increases. **1 GB** is a good starting point for many smaller installations.

![Check Swap Space and SSH options](https://support.ping64.nl/logos/image-1780759059023-528023667.png)

7. Start the installation.

If you are not using an SSH key, the panel may ask you to confirm that you want to install without one. Check this carefully and only confirm if this is correct.

The installation usually takes a few minutes. Wait until the task is complete and the VPS is active.

## Opening Dokploy

After installation, you can open Dokploy in your browser. Use your VPS IP address with port **3000**:

```text
http://your-vps-ip:3000
```

On your first visit, you will create an admin account for Dokploy. Choose a strong password and store the login details safely.

## What now?

Your VPS is now running Dokploy. Continue with the article about the first steps in Dokploy:

[**Getting Started with Dokploy on Your Etheron VPS**](https://support.etheron.nl/artikel/getting-started-with-dokploy-on-your-etheron-vps)

If it does not work, feel free to reach out via [Discord](https://etheron.nl/discord) or create a [support ticket](https://mijn.etheron.nl/submitticket.php).

In this article, we explain how to install Dokploy on your Etheron VPS using the one-click app.

How can we help you?

Featured + Popular Articles

All categories