Web Terminal

Access your server directly from the browser without needing to configure SSH on your computer.

Accessing the Terminal

1. Go to your Dashboard and select a deployment
2. In the "Advanced Tools" section, click on "Terminal"
3. The terminal will open in a modal window

Automatic Connection

The terminal connects automatically using your deployment's credentials. You don't need to remember passwords.

Help Button

In the upper corner of the modal, you'll see a help button (?) that takes you directly to this documentation.

Connection Types

The terminal allows you to connect to two different places:

Host (VPS)

Direct connection to the server. You have full system access:

• View all containers with docker ps
• Modify system files
• Install packages
• Restart services

Individual Containers

Connection inside a specific container. Useful for:

• Application debugging
• Viewing files inside the container
• Running app-specific commands
• Accessing the application console

How to Select the Destination

When you open the terminal, you'll see a dropdown at the top:

Connect to: [Host (VPS)     ]

The dropdown includes:

• Host (VPS): Full server access
• n8n_app: Application container
• n8n_db: Database container
• redis: Cache container (if applicable)

Simply select the destination from the dropdown. The terminal will reconnect automatically.

When you select a container, you'll see a badge showing the executed command:

docker exec -it n8n_app

Available Containers

The containers you see depend on your application. For example:

• n8n: n8n_app, n8n_db, redis
• WordPress: wordpress_app, wordpress_db
• Ghost: ghost_app, ghost_db

When to Use Each One

Use the Host when you need to:

• Check the overall server status
• Restart Docker or the entire application
• Modify system configuration
• View Docker logs
• Manage disk space

Use a Container when you need to:

• Debug application issues
• Access the app's command console
• View internal container files
• Run application scripts

Useful Commands

On the Host (VPS)

# View all containers
docker ps

# View logs for the entire application
docker compose logs -f --tail=100

# Restart the application
docker compose restart

# Check disk usage
df -h

# Check memory usage
free -h

# View active processes
htop

Inside a Container

# View app files
ls -la /app

# View environment variables
env

# Search for a file
find / -name "file.txt"

# View container processes
ps aux

Commands by Application

n8n

# You're already in the n8n_app container
# View workflows
ls -la /home/node/.n8n/

# View configuration
cat /home/node/.n8n/config

WordPress

# In the wordpress_app container
# Use WP-CLI
wp core version
wp plugin list
wp user list

PostgreSQL

# In the database container
psql -U postgres
\l   # List databases
\dt  # List tables

Keyboard Shortcuts

Shortcut	Action
Ctrl + C	Cancel current command
Ctrl + L	Clear screen
Ctrl + D	Close session
Tab	Autocomplete
Up / Down	Navigate history

File Navigation (Host)

# Go to the app folder
cd /app

# View files
ls -la

# View file contents
cat docker-compose.yml

# Edit file (simple editor)
nano file.txt

Important Folders (Host)

Folder	Contents
/app	Your application files
/app/docker-compose.yml	Docker configuration
/app/.env	Environment variables
/opt/deployalo	Deployalo agent
/var/log	System logs

Troubleshooting

Terminal won't connect

1. Verify that your deployment is in "Running" status
2. Wait a few seconds and reload the page
3. If it persists, restart the deployment from the panel

"Container not found"

If you see this error when selecting a container:

1. The container may be restarting
2. Go to the Host and run docker ps to see the exact names
3. If the container doesn't appear, the app may have issues

Commands not responding

If a command gets "stuck":

1. Press Ctrl + C to cancel
2. If that doesn't work, close and reopen the terminal

No bash in the container

Some minimalist containers (Alpine Linux) only have sh:

# If bash isn't available, use:
sh
# Or:
/bin/sh

Permission errors

On the Host: All commands run as root. If you see permission errors, it may be a Docker volumes issue:

# Check file permissions
ls -la /app/data/

# Change permissions if needed
chmod -R 755 /app/data/

In a Container: Each container has its own user. Some commands may require root:

# If you need root inside the container
# Close the terminal and connect to the Host
# Then:
docker exec -u root -it container_name sh

Security

Important

The terminal has full access to the server or container. Be careful with the commands you run:

• rm -rf can delete important files
• Don't share your screen while using the terminal
• Close the terminal when you're done
• Changes in containers may be lost if they restart

Technical Differences

Feature	Host (VPS)	Container
User	root	Container user
Persistence	Permanent	May be lost on restart
Scope	Entire server	Container only
Docker	Available	Not available
Base system	Ubuntu/Debian	Depends on image

Limitations

• Session timeout: 30 minutes of inactivity
• Does not support graphical interface applications
• Some special characters may not work correctly
• Changing destination closes the current session