<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ServerStadium Archives - ServerStadium</title>
	<atom:link href="https://serverstadium.com/knowledge-base/tag/serverstadium/feed/" rel="self" type="application/rss+xml" />
	<link>https://serverstadium.com/knowledge-base/tag/serverstadium/</link>
	<description>Public Cloud Solution by ServerStadium</description>
	<lastBuildDate>Tue, 12 Aug 2025 18:28:30 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://serverstadium.com/wp-content/uploads/2023/04/cropped-favicon-1-32x32.png</url>
	<title>ServerStadium Archives - ServerStadium</title>
	<link>https://serverstadium.com/knowledge-base/tag/serverstadium/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>YOURLS: Branded URL Shortener on a Dedicated Server</title>
		<link>https://serverstadium.com/knowledge-base/yourls-url-shortener-dedicated-servers/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Tue, 12 Aug 2025 18:28:26 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=12203</guid>

					<description><![CDATA[<p>Introduction Run a branded URL shortener with YOURLS on a ServerStadium dedicated server (or ServerStadium VM). This guide sets up YOURLS on Ubuntu&#160;24.04 with Nginx, PHP&#160;8.3, MariaDB/MySQL, and automatic HTTPS via Let’s Encrypt—so your team gets short links, click analytics, and a simple admin UI on your own domain. Prerequisites A ServerStadium dedicated server or&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/yourls-url-shortener-dedicated-servers/">YOURLS: Branded URL Shortener on a Dedicated Server</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Introduction</h2>



<p class="wp-block-paragraph">Run a branded URL shortener with <strong>YOURLS</strong> on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=yourls">ServerStadium dedicated server</a> (or <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=yourls">ServerStadium VM</a>). This guide sets up YOURLS on Ubuntu&nbsp;24.04 with Nginx, PHP&nbsp;8.3, MariaDB/MySQL, and automatic HTTPS via Let’s Encrypt—so your team gets short links, click analytics, and a simple admin UI on your own domain.</p>



<h2 class="wp-block-heading">Prerequisites</h2>



<ul class="wp-block-list">
  <li>A <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=yourls">ServerStadium dedicated server</a> or <a href="https://serverstadium.com/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=yourls">VM</a> running Ubuntu&nbsp;24.04.</li>
  <li>A domain like <code>sho.rt</code> or <code>yourls.example.com</code> pointing to your server’s public IP.</li>
  <li>SSH access with a sudo-capable user and an email address for Let’s Encrypt notices.</li>
</ul>



<h2 class="wp-block-heading">Step 1 — Install Nginx, PHP-FPM, and MariaDB</h2>


<pre><code>sudo apt update && sudo apt -y upgrade
sudo apt -y install nginx mariadb-server \
  php8.3-fpm php8.3-mysql php8.3-curl php8.3-xml php8.3-mbstring php8.3-gd php8.3-zip php8.3-intl \
  unzip curl certbot python3-certbot-nginx

sudo systemctl enable --now nginx mariadb php8.3-fpm
</code></pre>


<h2 class="wp-block-heading">Step 2 — Create the Database</h2>


<pre><code>sudo mysql_secure_installation

sudo mysql -e "CREATE DATABASE yourls DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;"
sudo mysql -e "CREATE USER 'yourlsuser'@'localhost' IDENTIFIED BY 'ChangeThisStrongPassword!';"
sudo mysql -e "GRANT ALL PRIVILEGES ON yourls.* TO 'yourlsuser'@'localhost'; FLUSH PRIVILEGES;"
</code></pre>


<h2 class="wp-block-heading">Step 3 — Download YOURLS (Latest Stable) and Deploy</h2>



<p class="wp-block-paragraph">This uses the current stable release (1.10.2). Adjust if a newer stable version is available.</p>


<pre><code>sudo mkdir -p /var/www/yourls
cd /tmp
wget -O yourls.tar.gz https://github.com/YOURLS/YOURLS/archive/refs/tags/1.10.2.tar.gz
tar -xzf yourls.tar.gz
sudo rsync -a YOURLS-1.10.2/ /var/www/yourls/
sudo chown -R www-data:www-data /var/www/yourls
</code></pre>


<h2 class="wp-block-heading">Step 4 — Configure YOURLS</h2>


<pre><code># Create the user config directory
sudo mkdir -p /var/www/yourls/user

# Generate a cookie key
CK=$(openssl rand -base64 48)

# Write config.php (edit domain, users, and passwords as needed)
sudo tee /var/www/yourls/user/config.php >/dev/null <<EOF
&lt;?php
/* MySQL settings */
define( 'YOURLS_DB_USER', 'yourlsuser' );
define( 'YOURLS_DB_PASS', 'ChangeThisStrongPassword!' );
define( 'YOURLS_DB_NAME', 'yourls' );
define( 'YOURLS_DB_HOST', 'localhost' );
define( 'YOURLS_DB_PREFIX', 'yourls_' );

/* Site options */
define( 'YOURLS_SITE', 'https://yourls.example.com' ); // your short domain, no trailing slash
define( 'YOURLS_PRIVATE', true );                       // admin area requires login
define( 'YOURLS_UNIQUE_URLS', true );
define( 'YOURLS_COOKIEKEY', '$CK' );                    // random secret key

/* Admin user(s) */
$yourls_user_passwords = array(
  'admin' => 'ChangeThisStrongPassword!'                // set a strong password
);

/* Optional locale and timezone */
// define( 'YOURLS_LANG', '' );
// define( 'YOURLS_HOURS_OFFSET', 0 );
EOF

sudo chown www-data:www-data /var/www/yourls/user/config.php
sudo chmod 440 /var/www/yourls/user/config.php
</code></pre>


<h2 class="wp-block-heading">Step 5 — Nginx Server Block + PHP-FPM</h2>


<pre><code>sudo tee /etc/nginx/sites-available/yourls >/dev/null <<'EOF'
server {
    listen 80;
    listen [::]:80;
    server_name yourls.example.com;

    root /var/www/yourls;
    index index.php;

    # YOURLS loader: route all unmatched paths to yourls-loader.php
    location / {
        try_files $uri $uri/ /yourls-loader.php$is_args$args;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/run/php/php8.3-fpm.sock;
    }

    # Security: deny access to hidden files (except .well-known for ACME)
    location ~ /\.(?!well-known) {
        deny all;
    }
}
EOF

sudo ln -s /etc/nginx/sites-available/yourls /etc/nginx/sites-enabled/yourls
sudo nginx -t &#038;&#038; sudo systemctl reload nginx
</code></pre>


<h2 class="wp-block-heading">Step 6 — Enable HTTPS (Let’s Encrypt)</h2>


<pre><code>sudo certbot --nginx -d yourls.example.com --redirect -m you@example.com --agree-tos -n
</code></pre>


<h2 class="wp-block-heading">Step 7 — Run the Installer &amp; Log In</h2>



<ul class="wp-block-list">
  <li>Open <code>https://yourls.example.com/admin/install.php</code> to create the database tables.</li>
  <li>Then go to <code>https://yourls.example.com/admin/</code> and log in with the admin user configured in <code>config.php</code>.</li>
  <li>Create your first branded short link and share it!</li>
</ul>



<h2 class="wp-block-heading">Optional: Public API &amp; Plugins</h2>



<ul class="wp-block-list">
  <li>For team usage only, keep YOURLS private (default). If you want a public API, set <code>define('YOURLS_PRIVATE_API', false);</code> in <code>config.php</code>.</li>
  <li>Explore plugins (rate limiting, QR codes, custom keywords) from the YOURLS ecosystem to extend functionality.</li>
</ul>



<h2 class="wp-block-heading">Firewall &amp; Service Checks</h2>


<pre><code>sudo ufw allow OpenSSH
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable
sudo systemctl status nginx php8.3-fpm --no-pager
</code></pre>


<h2 class="wp-block-heading">Troubleshooting</h2>



<ul class="wp-block-list">
  <li><strong>Blank/403 at root:</strong> YOURLS intentionally doesn’t show a homepage—use <code>/admin/</code> for the UI. Short URLs still resolve from the root.</li>
  <li><strong>PHP errors:</strong> Ensure PHP&nbsp;8.1+ is installed and FPM socket path matches your version (Ubuntu&nbsp;24.04 uses <code>/run/php/php8.3-fpm.sock</code>).</li>
  <li><strong>Short links 404:</strong> Confirm your Nginx block contains <code>try_files $uri $uri/ /yourls-loader.php$is_args$args;</code> and you reloaded Nginx.</li>
  <li><strong>HTTPS fails:</strong> Check DNS A/AAAA records and re-run <code>certbot --nginx</code>. Inspect logs via <code>journalctl -u nginx -n 100 --no-pager</code>.</li>
</ul>



<p class="wp-block-paragraph">Want an easy, affordable start? Choose an instant <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=yourls">ServerStadium dedicated server</a> and brand your links today.</p>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">With YOURLS on ServerStadium, you control your data, domain, and analytics—all secured over HTTPS. For more help or information about ServerStadium services, visit our <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=yourls">knowledge base</a> or the <a href="https://serverstadium.com/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=yourls">ServerStadium website</a>.</p>

<p>The post <a href="https://serverstadium.com/knowledge-base/yourls-url-shortener-dedicated-servers/">YOURLS: Branded URL Shortener on a Dedicated Server</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Jellyfin Media Server: Movies and Music on a Dedicated Server</title>
		<link>https://serverstadium.com/knowledge-base/jellyfin-media-server-dedicated-servers/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Tue, 12 Aug 2025 18:22:44 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=12201</guid>

					<description><![CDATA[<p>Introduction Set up your own Netflix-style library with Jellyfin on a ServerStadium dedicated server or VM. This guide covers a clean Ubuntu&#160;24.04 install, creating media folders, enabling a secure HTTPS site with Nginx + Let’s Encrypt, and basic multi-user setup. Prerequisites A ServerStadium dedicated server or VM running Ubuntu&#160;24.04. SSH access with a sudo-capable user.&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/jellyfin-media-server-dedicated-servers/">Jellyfin Media Server: Movies and Music on a Dedicated Server</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Introduction</h2>



<p class="wp-block-paragraph">Set up your own Netflix-style library with <strong>Jellyfin</strong> on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> or <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">VM</a>. This guide covers a clean Ubuntu&nbsp;24.04 install, creating media folders, enabling a secure HTTPS site with Nginx + Let’s Encrypt, and basic multi-user setup.</p>



<h2 class="wp-block-heading">Prerequisites</h2>



<ul class="wp-block-list">
  <li>A <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> or <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">VM</a> running Ubuntu&nbsp;24.04.</li>
  <li>SSH access with a sudo-capable user.</li>
  <li>A domain/subdomain (e.g., <code>media.example.com</code>) pointing to your server’s public IP.</li>
</ul>



<h2 class="wp-block-heading">Step 1 — Install Jellyfin (Official Repo Script)</h2>



<p class="wp-block-paragraph">The official installer adds the repository and installs Jellyfin and its codecs.</p>


<pre><code>sudo apt update && sudo apt -y install curl gnupg apt-transport-https ca-certificates
curl https://repo.jellyfin.org/install-debuntu.sh | sudo bash
# If needed, ensure installed:
sudo apt -y install jellyfin
sudo systemctl enable --now jellyfin
sudo systemctl status jellyfin --no-pager
</code></pre>


<h2 class="wp-block-heading">Step 2 — Create Media Folders &amp; Permissions</h2>


<pre><code>sudo mkdir -p /srv/media/{movies,tv,music}
# Jellyfin runs as the "jellyfin" user by default
sudo chown -R jellyfin:jellyfin /srv/media
</code></pre>


<p class="wp-block-paragraph">If you mount additional disks (e.g., at <code>/srv/media</code>), ensure ownership stays with <code>jellyfin:jellyfin</code> or grant group read access as needed.</p>



<h2 class="wp-block-heading">Step 3 — First-Run Wizard</h2>



<ul class="wp-block-list">
  <li>Temporarily open the local port to finish setup: <code>sudo ufw allow 8096/tcp</code></li>
  <li>Browse to <code>http://&lt;server-ip&gt;:8096</code>, create the admin account, and add libraries pointing to <code>/srv/media/movies</code>, <code>/srv/media/tv</code>, <code>/srv/media/mus ic</code>.</li>
  <li>In <em>Dashboard → Networking</em>, leave HTTP at <code>8096</code>. We’ll put HTTPS behind Nginx next.</li>
</ul>



<h2 class="wp-block-heading">Step 4 — Secure HTTPS with Nginx Reverse Proxy</h2>



<p class="wp-block-paragraph">We’ll proxy Jellyfin (localhost:8096) behind Nginx on <code>media.example.com</code> with a free Let’s Encrypt certificate.</p>


<pre><code>sudo apt -y install nginx certbot python3-certbot-nginx

# Create the proxy config
sudo tee /etc/nginx/sites-available/jellyfin &gt;/dev/null &lt;&lt;'EOF'
server {
    listen 80;
    listen [::]:80;
    server_name media.example.com;
    return 301 https://$host$request_uri;
}

server {
    # For Nginx 1.25+: enable HTTP/2 explicitly
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;

    server_name media.example.com;

    # Let’s Encrypt paths (created by certbot)
    ssl_certificate /etc/letsencrypt/live/media.example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/media.example.com/privkey.pem;
    include /etc/letsencrypt/options-ssl-nginx.conf;
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;

    # Increase upload size for posters, etc.
    client_max_body_size 20M;

    # Upstream Jellyfin (local)
    set $jellyfin 127.0.0.1;

    location / {
        proxy_pass http://$jellyfin:8096;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Protocol $scheme;
        proxy_set_header X-Forwarded-Host $http_host;
        proxy_buffering off;  # better for streaming
    }

    # WebSocket endpoint
    location /socket {
        proxy_pass http://$jellyfin:8096;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Protocol $scheme;
        proxy_set_header X-Forwarded-Host $http_host;
    }
}
EOF

# Enable the site and get a certificate
sudo ln -s /etc/nginx/sites-available/jellyfin /etc/nginx/sites-enabled/jellyfin
sudo nginx -t && sudo systemctl reload nginx
sudo certbot --nginx -d media.example.com --redirect -m you@example.com --agree-tos -n

# Lock down the firewall for public access via HTTPS only
sudo ufw allow OpenSSH
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw deny 8096/tcp
sudo ufw enable
sudo ufw status
</code></pre>


<p class="wp-block-paragraph">In Jellyfin <em>Dashboard → Networking</em>, add your reverse proxy to <strong>Known Proxies</strong> (e.g., <code>127.0.0.1</code> and your server’s private IP). This ensures client IPs are passed correctly through Nginx.</p>



<h2 class="wp-block-heading">Step 5 — Create Users &amp; Manage Libraries</h2>



<ul class="wp-block-list">
  <li>Go to <em>Dashboard → Users → +</em> to add family/teammates. Assign libraries and playback permissions.</li>
  <li>Use <em>Dashboard → Libraries</em> to add or rescan folders as you upload media to <code>/srv/media</code>.</li>
  <li>For remote streaming, keep originals reasonable in size/bitrate or pre-encode to H.264/H.265 for smoother playback on modest CPUs.</li>
</ul>



<h2 class="wp-block-heading">Optional: Service &amp; Updates</h2>


<pre><code># Check service status / logs
sudo systemctl status jellyfin --no-pager
journalctl -u jellyfin -n 100 --no-pager

# Update Jellyfin when new releases arrive
sudo apt update && sudo apt -y upgrade
</code></pre>


<h2 class="wp-block-heading">Troubleshooting</h2>



<ul class="wp-block-list">
  <li><strong>Can’t reach HTTPS site:</strong> Confirm DNS points to your server; re-run Certbot and check <code>sudo nginx -t</code> and <code>journalctl -u nginx</code>.</li>
  <li><strong>Direct port works but proxy fails:</strong> Verify Nginx site is enabled and Jellyfin is listening on <code>8096</code>; restart both services.</li>
  <li><strong>Wrong client IPs:</strong> Add Nginx to <em>Known Proxies</em> in Jellyfin networking settings and reload.</li>
  <li><strong>Playback stutters:</strong> Prefer direct play/stream-copy codecs and wired networking; reduce transcode quality if CPU is saturated.</li>
</ul>



<p class="wp-block-paragraph">Ready to stream? Launch on an instant, low-cost <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium dedicated server</a> for reliable bandwidth and storage.</p>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">You now have a secure Jellyfin media server with user accounts and HTTPS, ready for movies, TV, and music—hosted on fast, dependable ServerStadium hardware. For more help or information about ServerStadium services, visit our <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">knowledge base</a> or the <a href="https://serverstadium.com/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium website</a>.</p>

<p>The post <a href="https://serverstadium.com/knowledge-base/jellyfin-media-server-dedicated-servers/">Jellyfin Media Server: Movies and Music on a Dedicated Server</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Set Up a Basic FTP/Secure FTP Server with vsftpd</title>
		<link>https://serverstadium.com/knowledge-base/vsftpd-ftp-sftp-on-dedicated-servers/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Tue, 12 Aug 2025 18:19:02 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=12199</guid>

					<description><![CDATA[<p>Introduction This guide will walk you through installing and configuring vsftpd for FTP and FTPS (TLS) on a ServerStadium VM or a dedicated server running Ubuntu&#160;24.04. You’ll also set up SFTP access using OpenSSH, create user accounts locked to their own folders, and open only the ports you need. Note on terminology: “Secure FTP” can&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/vsftpd-ftp-sftp-on-dedicated-servers/">Set Up a Basic FTP/Secure FTP Server with vsftpd</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Introduction</h2>



<p class="wp-block-paragraph">This guide will walk you through installing and configuring <strong>vsftpd</strong> for FTP and FTPS (TLS) on a <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium VM</a> or a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">dedicated server</a> running Ubuntu&nbsp;24.04. You’ll also set up <strong>SFTP</strong> access using OpenSSH, create user accounts locked to their own folders, and open only the ports you need.</p>



<p class="wp-block-paragraph"><em>Note on terminology:</em> “Secure FTP” can mean <strong>FTPS</strong> (FTP over TLS, handled by vsftpd) or <strong>SFTP</strong> (SSH File Transfer Protocol, handled by the SSH server). This tutorial covers both.</p>



<h2 class="wp-block-heading">Prerequisites</h2>



<ul class="wp-block-list">
  <li>A <a href="https://serverstadium.com/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium VM</a> or <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">dedicated server</a> running Ubuntu&nbsp;24.04 (or similar).</li>
  <li>SSH access with a sudo-capable user.</li>
  <li>A domain (e.g., <code>ftp.example.com</code>) if you plan to enable FTPS with Let’s Encrypt.</li>
</ul>



<h2 class="wp-block-heading">Part A — Install vsftpd and Configure FTPS (Explicit TLS)</h2>



<p class="wp-block-paragraph"><strong>1) Install packages and create a base directory for FTP users</strong></p>


<pre><code>sudo apt update &amp;&amp; sudo apt -y upgrade
sudo apt -y install vsftpd openssl ufw certbot
sudo mkdir -p /srv/ftp/users
sudo chown root:root /srv/ftp
sudo chmod 755 /srv/ftp
</code></pre>


<p class="wp-block-paragraph"><strong>2) Prepare vsftpd user allowlist and passive ports</strong></p>


<pre><code># Only users listed here will be allowed to log in via FTP/FTPS
echo "ftpuser1" | sudo tee -a /etc/vsftpd.userlist

# Open a small passive port range (adjust as needed)
echo "40000 40100" | sudo tee /etc/vsftpd.passive.ports >/dev/null
</code></pre>


<p class="wp-block-paragraph"><strong>3) Generate or obtain a TLS certificate</strong></p>



<ul class="wp-block-list">
  <li><em>Recommended (public domain):</em> Use Let’s Encrypt standalone challenge (port 80 must be reachable):<br>
  <code>sudo systemctl stop vsftpd</code><br>
  <code>sudo certbot certonly --standalone -d ftp.example.com -m you@example.com --agree-tos -n</code><br>
  Certificates will be under <code>/etc/letsencrypt/live/ftp.example.com/</code>.</li>
  <li><em>Or self-signed (lab use):</em> <code>sudo openssl req -x509 -nodes -newkey rsa:4096 -keyout /etc/ssl/private/vsftpd.key -out /etc/ssl/certs/vsftpd.crt -days 825</code></li>
</ul>



<p class="wp-block-paragraph"><strong>4) Configure vsftpd</strong></p>


<pre><code>sudo cp /etc/vsftpd.conf /etc/vsftpd.conf.bak

sudo tee /etc/vsftpd.conf &gt;/dev/null &lt;&lt;'EOF'
listen=YES
listen_ipv6=NO

# Local user access
local_enable=YES
write_enable=YES
chroot_local_user=YES
allow_writeable_chroot=YES

# Limit logins to an allowlist
userlist_enable=YES
userlist_file=/etc/vsftpd.userlist
userlist_deny=NO

# User home mapping under /srv/ftp/users/$USER
user_sub_token=$USER
local_root=/srv/ftp/users/$USER

# Passive mode (open these in firewall)
pasv_enable=YES
pasv_min_port=40000
pasv_max_port=40100
# If behind NAT, set your public IP:
# pasv_address=203.0.113.10

# TLS (Explicit FTPS via AUTH TLS)
ssl_enable=YES
allow_anon_ssl=NO
force_local_logins_ssl=YES
force_local_data_ssl=YES

# Use Let’s Encrypt paths if obtained; otherwise use self-signed
rsa_cert_file=/etc/letsencrypt/live/ftp.example.com/fullchain.pem
rsa_private_key_file=/etc/letsencrypt/live/ftp.example.com/privkey.pem
# rsa_cert_file=/etc/ssl/certs/vsftpd.crt
# rsa_private_key_file=/etc/ssl/private/vsftpd.key

# TLS hardening
ssl_tlsv1=NO
ssl_tlsv1_1=NO
ssl_tlsv1_2=YES
require_ssl_reuse=NO
ssl_ciphers=HIGH

# Logging
xferlog_std_format=NO
log_ftp_protocol=YES
EOF

sudo systemctl restart vsftpd
sudo systemctl enable vsftpd
</code></pre>


<p class="wp-block-paragraph"><strong>5) Create an FTP/FTPS user (chrooted to their own folder)</strong></p>


<pre><code>sudo adduser --home /srv/ftp/users/ftpuser1 --shell /usr/sbin/nologin ftpuser1
sudo mkdir -p /srv/ftp/users/ftpuser1
sudo chown -R ftpuser1:ftpuser1 /srv/ftp/users/ftpuser1

# Ensure the user is in the allowlist
echo "ftpuser1" | sudo tee -a /etc/vsftpd.userlist

# (Optional) Repeat for additional users
</code></pre>


<p class="wp-block-paragraph"><strong>6) Open only required firewall ports</strong></p>


<pre><code># Control channel (21) + passive range + SSH (for SFTP, Part B)
sudo ufw allow 21/tcp
sudo ufw allow 40000:40100/tcp
sudo ufw allow OpenSSH
sudo ufw enable
sudo ufw status
</code></pre>


<h2 class="wp-block-heading">Part B — Enable SFTP (SSH File Transfer) with Chroot</h2>



<p class="wp-block-paragraph">SFTP uses the SSH server (not vsftpd). We’ll create a restricted SFTP group whose members are locked to their own directories.</p>


<pre><code># Create an SFTP-only group
sudo groupadd sftpusers

# Create base directories; chroot requires the chroot path to be root-owned and not writable by the user
sudo mkdir -p /srv/sftp
sudo chown root:root /srv/sftp
sudo chmod 755 /srv/sftp

# Example SFTP user
sudo useradd -m -d /srv/sftp/sftpuser1 -s /usr/sbin/nologin -G sftpusers sftpuser1
sudo passwd sftpuser1

# Create a writable subfolder inside the chroot
sudo mkdir -p /srv/sftp/sftpuser1/upload
sudo chown sftpuser1:sftpuser1 /srv/sftp/sftpuser1/upload
sudo chmod 750 /srv/sftp/sftpuser1/upload
</code></pre>


<p class="wp-block-paragraph">Edit the SSH daemon configuration to force SFTP and chroot users in the <code>sftpusers</code> group:</p>


<pre><code>sudo cp /etc/ssh/sshd_config /etc/ssh/sshd_config.bak

sudo tee -a /etc/ssh/sshd_config &gt;/dev/null &lt;&lt;'EOF'

# SFTP-only jail for sftpusers
Subsystem sftp internal-sftp

Match Group sftpusers
  ChrootDirectory /srv/sftp/%u
  ForceCommand internal-sftp
  X11Forwarding no
  AllowTcpForwarding no
EOF

sudo systemctl restart ssh
</code></pre>


<p class="wp-block-paragraph">Users in <code>sftpusers</code> now connect with any SFTP client (port 22) and are jailed to <code>/srv/sftp/&lt;username&gt;</code> with write access limited to the <code>upload</code> subfolder.</p>



<h2 class="wp-block-heading">Connectivity &amp; Client Settings</h2>



<ul class="wp-block-list">
  <li><strong>FTPS (Explicit):</strong> Use your FTP client’s “FTP over TLS (explicit)” mode, host <code>ftp.example.com</code>, port <code>21</code>, enable passive mode, and trust the certificate (Let’s Encrypt recommended).</li>
  <li><strong>SFTP:</strong> Use the SFTP protocol (not FTP) on host <code>ftp.example.com</code> (or your server IP), port <code>22</code>.</li>
</ul>



<h2 class="wp-block-heading">Troubleshooting</h2>



<ul class="wp-block-list">
  <li><strong>FTPS handshake fails:</strong> Verify certificate paths in <code>/etc/vsftpd.conf</code>, confirm DNS points to your server, and ensure ports 21 and 40000–40100/tcp are open.</li>
  <li><strong>Login denied (FTP):</strong> Make sure the username is listed in <code>/etc/vsftpd.userlist</code>.</li>
  <li><strong>SFTP chroot error:</strong> Ensure <code>/srv/sftp/&lt;user&gt;</code> is owned by <code>root:root</code> and not writable; use a writable subfolder for uploads.</li>
  <li><strong>Behind NAT:</strong> Set <code>pasv_address=&lt;public_ip&gt;</code> in <code>/etc/vsftpd.conf</code> and forward the passive range on your firewall.</li>
  <li><strong>Logs:</strong> Check <code>/var/log/syslog</code> and <code>/var/log/auth.log</code> for SSH/SFTP; for vsftpd, enable <code>log_ftp_protocol=YES</code> (already set).</li>
</ul>



<p class="wp-block-paragraph">Need a quick start? Spin up an instant, low-cost <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium dedicated server</a> and deploy secure file transfer in minutes.</p>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">You’ve set up FTP/FTPS with vsftpd and SFTP with OpenSSH, created locked-down user areas, and opened only the necessary ports—perfect for client uploads and internal file exchange. For more help or information about ServerStadium services, visit our <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">knowledge base</a> or the <a href="https://serverstadium.com/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium website</a>.</p>

<p>The post <a href="https://serverstadium.com/knowledge-base/vsftpd-ftp-sftp-on-dedicated-servers/">Set Up a Basic FTP/Secure FTP Server with vsftpd</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Easy Duplicati Backups on Ubuntu for Dedicated Servers</title>
		<link>https://serverstadium.com/knowledge-base/easy-duplicati-backups-on-ubuntu-for-dedicated-servers/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Tue, 12 Aug 2025 18:16:06 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=12197</guid>

					<description><![CDATA[<p>Introduction This beginner-friendly guide walks you through installing Duplicati (open-source backup with a simple web UI) on Ubuntu 24.04 running on a ServerStadium dedicated server. You’ll set a secure admin password, reach the web UI from your network, schedule encrypted backups, and send email reports. If you don’t have a server yet, spin up an&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/easy-duplicati-backups-on-ubuntu-for-dedicated-servers/">Easy Duplicati Backups on Ubuntu for Dedicated Servers</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Introduction</h2>



<p class="wp-block-paragraph">This beginner-friendly guide walks you through installing <strong>Duplicati</strong> (open-source backup with a simple web UI) on Ubuntu 24.04 running on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a>. You’ll set a secure admin password, reach the web UI from your network, schedule encrypted backups, and send email reports. If you don’t have a server yet, spin up an <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">instant dedicated server</a> and follow along.</p>



<h2 class="wp-block-heading">Prerequisites</h2>



<ul class="wp-block-list">
  <li>A <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> running Ubuntu 24.04 (or similar).</li>
  <li>SSH access with <code>sudo</code> privileges.</li>
  <li>A workstation on the same network (or VPN) to access the web UI.</li>
</ul>



<h2 class="wp-block-heading">Step 1 — Update and Basics</h2>



<p class="wp-block-paragraph">Update packages and install a few helpers.</p>


<pre><code>sudo apt-get update && sudo apt-get upgrade -y
sudo apt-get install -y curl gnupg ufw</code></pre>


<h2 class="wp-block-heading">Step 2 — Install Duplicati (.deb package)</h2>



<p class="wp-block-paragraph">Download a current stable Debian/Ubuntu package and install it (example below). Adjust the version if a newer stable build is available.</p>


<pre><code>cd /tmp
wget https://updates.duplicati.com/stable/duplicati-2.1.0.5_stable_2025-03-04-linux-x64-gui.deb
sudo apt-get install -y ./duplicati-2.1.0.5_stable_2025-03-04-linux-x64-gui.deb

sudo systemctl enable duplicati
sudo systemctl start duplicati
sudo systemctl status duplicati --no-pager</code></pre>


<p class="wp-block-paragraph">By default, Duplicati’s server listens on port <code>8200</code> and only on <code>localhost</code>. We’ll securely expose it next so you can reach it from your LAN.</p>



<h2 class="wp-block-heading">Step 3 — One-Time Secure Setup (password &amp; remote access)</h2>



<p class="wp-block-paragraph">Set an initial web password and temporarily allow access from your network so you can finish setup in the browser:</p>


<pre><code># Stop the service
sudo systemctl stop duplicati

# Start Duplicati manually one time with a strong password and LAN access
# Replace YOUR_STRONG_PASSWORD and YOUR_SERVER_IP
nohup /usr/bin/duplicati-server \
  --webservice-password=YOUR_STRONG_PASSWORD \
  --webservice-interface=any \
  --webservice-port=8200 \
  --server-datafolder=/var/lib/duplicati \
  >/var/log/duplicati-initial.log 2>&1 &

# From your workstation, browse to:
#   http://YOUR_SERVER_IP:8200
# Sign in with the password above, open Settings, enable remote access if prompted, and Save.

# Then return to the server and switch back to the service:
sudo pkill -f duplicati-server
sudo systemctl start duplicati
sudo systemctl status duplicati --no-pager</code></pre>


<h2 class="wp-block-heading">Step 4 — Lock Down the Port (UFW)</h2>



<p class="wp-block-paragraph">Allow only your admin IP (replace <code>198.51.100.10</code>) to reach the Duplicati UI on port 8200.</p>


<pre><code>sudo ufw allow from 198.51.100.10 to any port 8200 proto tcp
sudo ufw enable
sudo ufw status</code></pre>


<p class="wp-block-paragraph">For public exposure, consider placing Duplicati behind a reverse proxy with HTTPS. For most beginners, restricting to an admin IP is simplest and safest.</p>



<h2 class="wp-block-heading">Step 5 — First Backup (Web UI)</h2>



<ul class="wp-block-list">
  <li>In the Duplicati UI → <strong>Add backup</strong>.</li>
  <li>Choose <strong>Configure a new backup</strong>, set a <strong>Backup name</strong> and <strong>Passphrase</strong> (AES-256 encryption).</li>
  <li><strong>Destination</strong>: pick storage you control (local folder, SFTP, WebDAV, or any S3-compatible service you use).</li>
  <li><strong>Source data</strong>: select folders to protect (e.g., <code>/etc</code>, <code>/var/www</code>, <code>/home</code>).</li>
  <li><strong>Schedule</strong>: daily or hourly, with a practical retention (e.g., “smart” or 30–60 days).</li>
  <li><strong>Save</strong> and run your first backup.</li>
</ul>



<h2 class="wp-block-heading">Optional — Email Reports (Postfix + mailutils)</h2>



<p class="wp-block-paragraph">Install basic mail tools and, if needed, configure an SMTP relay. Then enable reports under <strong>Settings → Send reports</strong> in Duplicati.</p>


<pre><code>sudo apt-get install -y postfix mailutils
# During Postfix setup, choose "Internet Site" and set the server's hostname.
# If using an SMTP relay, edit /etc/postfix/main.cf accordingly, then reload:
sudo systemctl reload postfix</code></pre>


<h2 class="wp-block-heading">Troubleshooting</h2>



<ul class="wp-block-list">
  <li><strong>UI won’t open:</strong> Confirm Duplicati is listening on 8200 and the firewall rule is correct:
    <br><code>sudo systemctl status duplicati</code>
    <br><code>ss -ltnp | grep 8200</code>
  </li>
  <li><strong>Can’t reach from LAN:</strong> Make sure you launched once with <code>--webservice-interface=any</code> and saved remote access in Settings. Then:
    <br><code>sudo systemctl restart duplicati</code>
  </li>
  <li><strong>Forgot the password:</strong> Stop the service, start once with an empty password to clear it, set a new one in Settings, then return to the service:
    <br><code>sudo systemctl stop duplicati</code>
    <br><code>/usr/bin/duplicati-server --webservice-password=</code>
    <br><code>sudo pkill -f duplicati-server && sudo systemctl start duplicati</code>
  </li>
</ul>



<h2 class="wp-block-heading">Why Host Duplicati on ServerStadium?</h2>



<ul class="wp-block-list">
  <li><strong>Instant dedicated servers</strong> with predictable CPU, RAM, and disk for consistent backup windows.</li>
  <li><strong>Scalable storage</strong> options and private networking for secure replication between nodes.</li>
  <li>Easy to grow from one backup host to a fleet. Get started here: <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium Dedicated Servers</a>.</li>
</ul>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">With Duplicati running on your ServerStadium dedicated server, you’ve got encrypted, scheduled backups managed from a clean web UI. Add more destinations, tune retention, and enable email reports for peace of mind. For more help or information about ServerStadium services, visit our <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">knowledge base</a> or the <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium website</a>.</p>

<p>The post <a href="https://serverstadium.com/knowledge-base/easy-duplicati-backups-on-ubuntu-for-dedicated-servers/">Easy Duplicati Backups on Ubuntu for Dedicated Servers</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Easy File Sharing with FileBrowser on a Dedicated Server</title>
		<link>https://serverstadium.com/knowledge-base/filebrowser-simple-file-sharing-dedicated-servers/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Tue, 12 Aug 2025 18:08:30 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=12195</guid>

					<description><![CDATA[<p>Introduction This guide will walk you through installing FileBrowser—a simple, web-based file manager—on a ServerStadium VM or a dedicated server running Ubuntu 24.04. You’ll set up FileBrowser as a service, secure it with HTTPS via Nginx and Let’s Encrypt, and create user accounts with scoped access for safe, point-and-click file sharing. Prerequisites A ServerStadium dedicated&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/filebrowser-simple-file-sharing-dedicated-servers/">Easy File Sharing with FileBrowser on a Dedicated Server</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Introduction</h2>



<p class="wp-block-paragraph">This guide will walk you through installing <strong>FileBrowser</strong>—a simple, web-based file manager—on a <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium VM</a> or a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">dedicated server</a> running Ubuntu 24.04. You’ll set up FileBrowser as a service, secure it with HTTPS via Nginx and Let’s Encrypt, and create user accounts with scoped access for safe, point-and-click file sharing.</p>



<h2 class="wp-block-heading">Prerequisites</h2>



<ul class="wp-block-list">
  <li>A <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium dedicated server</a> or <a href="https://serverstadium.com/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">VM</a> with Ubuntu 24.04.</li>
  <li>A domain (e.g., <code>files.example.com</code>) pointing to your server’s public IP.</li>
  <li>SSH access with a sudo-capable user and an email address for Let’s Encrypt notices.</li>
</ul>



<h2 class="wp-block-heading">Step 1 — Install FileBrowser (Official Script)</h2>



<p class="wp-block-paragraph">Use the project’s installer to fetch the latest binary:</p>


<pre><code>sudo apt update && sudo apt -y install curl unzip nginx certbot python3-certbot-nginx
curl -fsSL https://raw.githubusercontent.com/filebrowser/get/master/get.sh | bash
filebrowser version
</code></pre>


<p class="wp-block-paragraph">Create a dedicated system user and directories for data and config:</p>


<pre><code>sudo useradd --system --create-home --home-dir /srv/share --shell /usr/sbin/nologin filebrowser
sudo mkdir -p /srv/share /etc/filebrowser
sudo chown -R filebrowser:filebrowser /srv/share /etc/filebrowser
</code></pre>


<h2 class="wp-block-heading">Step 2 — Initialize Database &amp; Create Admin</h2>



<p class="wp-block-paragraph">Initialize FileBrowser’s database, then add an admin account.</p>


<pre><code># Initialize the database file
sudo -u filebrowser filebrowser -d /etc/filebrowser/filebrowser.db config init

# Create an admin user (change password!)
sudo -u filebrowser filebrowser -d /etc/filebrowser/filebrowser.db users add admin 'ChangeThisStrongPassword!' --perm.admin
</code></pre>


<h2 class="wp-block-heading">Step 3 — Run FileBrowser as a Service</h2>



<p class="wp-block-paragraph">Run FileBrowser on localhost:8080 and reverse-proxy it with Nginx for HTTPS.</p>


<pre><code>sudo tee /etc/systemd/system/filebrowser.service &gt;/dev/null &lt;&lt;'EOF'
[Unit]
Description=FileBrowser
After=network.target

[Service]
User=filebrowser
Group=filebrowser
WorkingDirectory=/srv/share
ExecStart=/usr/local/bin/filebrowser \
  --database /etc/filebrowser/filebrowser.db \
  --address 127.0.0.1 --port 8080 \
  --root /srv/share
Restart=on-failure

[Install]
WantedBy=multi-user.target
EOF

sudo systemctl daemon-reload
sudo systemctl enable --now filebrowser
sudo systemctl status filebrowser --no-pager
</code></pre>


<h2 class="wp-block-heading">Step 4 — Nginx Reverse Proxy with HTTPS</h2>



<p class="wp-block-paragraph">Create a simple Nginx server block for your domain that proxies to FileBrowser on localhost.</p>


<pre><code>sudo tee /etc/nginx/sites-available/filebrowser &gt;/dev/null &lt;&lt;'EOF'
server {
    listen 80;
    server_name files.example.com;

    location / {
        proxy_pass http://127.0.0.1:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}
EOF

sudo ln -s /etc/nginx/sites-available/filebrowser /etc/nginx/sites-enabled/filebrowser
sudo nginx -t && sudo systemctl reload nginx

# Issue and install a Let's Encrypt certificate
sudo certbot --nginx -d files.example.com --redirect -m you@example.com --agree-tos -n
</code></pre>


<h2 class="wp-block-heading">Step 5 — Create Regular Users with Scoped Access</h2>



<p class="wp-block-paragraph">Give each user their own folder (scope) so they only see what they should.</p>


<pre><code># Example: user 'alice' limited to /srv/share/users/alice
sudo mkdir -p /srv/share/users/alice
sudo chown -R filebrowser:filebrowser /srv/share/users

sudo -u filebrowser filebrowser -d /etc/filebrowser/filebrowser.db users add alice 'AnotherStrongPass!' \
  --scope /srv/share/users/alice \
  --perm.create --perm.delete --perm.download --perm.modify --perm.rename --perm.share
</code></pre>


<p class="wp-block-paragraph">Log in at <code>https://files.example.com</code> using the <code>admin</code> account to create additional users or adjust permissions in <em>Settings → User Management</em>.</p>



<h2 class="wp-block-heading">Optional: Brand, Sharing Links, and Basic Security</h2>



<ul class="wp-block-list">
  <li><strong>Branding:</strong> Set a name/logo in <em>Settings → Global Settings</em> or via CLI (e.g., <code>filebrowser config set --branding.name "Your Company"</code>).</li>
  <li><strong>Share links:</strong> Ensure users have the <em>share</em> permission, then use the “Share” action to generate links for clients and teammates.</li>
  <li><strong>Firewall:</strong> Allow web traffic and keep FileBrowser bound to localhost:
    <br><code>sudo ufw allow 80,443/tcp &amp;&amp; sudo ufw enable</code>
  </li>
</ul>



<h2 class="wp-block-heading">Troubleshooting</h2>



<ul class="wp-block-list">
  <li><strong>502/Bad Gateway:</strong> Check the service and Nginx logs:
    <br><code>journalctl -u filebrowser -n 100 --no-pager</code> &nbsp;and&nbsp; <code>journalctl -u nginx -n 100 --no-pager</code>.
  </li>
  <li><strong>Can’t log in:</strong> Reset a user’s password:
    <br><code>sudo -u filebrowser filebrowser -d /etc/filebrowser/filebrowser.db users update alice --password 'NewPass!'</code>
  </li>
  <li><strong>Permissions/visibility:</strong> Verify the user’s <em>scope</em> path and ownership under <code>/srv/share</code>; keep ownership with <code>filebrowser:filebrowser</code>.</li>
  <li><strong>SSL not issuing:</strong> Confirm DNS is pointing to your server and ports 80/443 are open; re-run <code>certbot --nginx</code>.</li>
</ul>



<p class="wp-block-paragraph">Need a quick, affordable start? Spin up an instant <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium dedicated server</a> and get FileBrowser online in minutes.</p>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">With FileBrowser running behind HTTPS on ServerStadium, you’ve got a clean, point-and-click way to share files securely with clients and teammates. For more help or information about ServerStadium services, visit our <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">knowledge base</a> or the <a href="https://serverstadium.com/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium website</a>.</p>

<p>The post <a href="https://serverstadium.com/knowledge-base/filebrowser-simple-file-sharing-dedicated-servers/">Easy File Sharing with FileBrowser on a Dedicated Server</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Install OpenCart on a ServerStadium Dedicated Server</title>
		<link>https://serverstadium.com/knowledge-base/opencart-on-dedicated-server-quickstart/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Tue, 12 Aug 2025 17:56:06 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=12190</guid>

					<description><![CDATA[<p>Introduction Launch a fast OpenCart store on a ServerStadium dedicated server (or ServerStadium VM) running Ubuntu 24.04. This quickstart walks beginners through installing OpenCart 4, enabling SEO-friendly URLs, adding free HTTPS via Let’s Encrypt, and getting sample data/themes in place—so you can start selling today on reliable ServerStadium hardware. Prerequisites A ServerStadium dedicated server or&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/opencart-on-dedicated-server-quickstart/">Install OpenCart on a ServerStadium Dedicated Server</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Introduction</h2>



<p class="wp-block-paragraph">Launch a fast OpenCart store on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> (or <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium VM</a>) running Ubuntu 24.04. This quickstart walks beginners through installing OpenCart 4, enabling SEO-friendly URLs, adding free HTTPS via Let’s Encrypt, and getting sample data/themes in place—so you can start selling today on reliable ServerStadium hardware.</p>



<h2 class="wp-block-heading">Prerequisites</h2>



<ul class="wp-block-list">
  <li>A <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium dedicated server</a> or <a href="https://serverstadium.com/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">VM</a> with Ubuntu 24.04 and a domain pointed to your server’s IP.</li>
  <li>SSH access with a sudo-capable user.</li>
  <li>An email address for Let’s Encrypt and an SMTP provider (for order emails).</li>
</ul>



<h2 class="wp-block-heading">Step 1 — Install LAMP and PHP Extensions</h2>



<p class="wp-block-paragraph">OpenCart 4 requires PHP 8.1+ with common extensions. Install Apache, MariaDB/MySQL, and PHP on Ubuntu 24.04:</p>


<pre><code>sudo apt update && sudo apt -y upgrade
sudo apt -y install apache2 mysql-server \
  php libapache2-mod-php php-mysql php-curl php-zip php-xml php-gd php-mbstring php-intl \
  unzip curl
sudo a2enmod rewrite
sudo systemctl enable --now apache2 mysql
</code></pre>


<h2 class="wp-block-heading">Step 2 — Create Database and User</h2>


<pre><code>sudo mysql_secure_installation

sudo mysql -e "CREATE DATABASE ocdb DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;"
sudo mysql -e "CREATE USER 'ocuser'@'localhost' IDENTIFIED BY 'ChangeThisStrongPassword!';"
sudo mysql -e "GRANT ALL PRIVILEGES ON ocdb.* TO 'ocuser'@'localhost'; FLUSH PRIVILEGES;"
</code></pre>


<h2 class="wp-block-heading">Step 3 — Download OpenCart 4.1.0.3</h2>



<p class="wp-block-paragraph">Grab the latest OpenCart 4 release and unpack it.</p>


<pre><code>cd /tmp
wget -O opencart.zip "https://sourceforge.net/projects/opencart.mirror/files/4.1.0.3/opencart-4.1.0.3.zip/download"
unzip opencart.zip
</code></pre>


<h2 class="wp-block-heading">Step 4 — Deploy Files and Set Permissions</h2>


<pre><code>sudo mkdir -p /var/www/opencart
# OpenCart zip contains an "upload" directory. Copy its contents to your web root.
sudo rsync -a upload/ /var/www/opencart/

# Rename config templates as required by the installer
sudo cp /var/www/opencart/config-dist.php /var/www/opencart/config.php
sudo cp /var/www/opencart/admin/config-dist.php /var/www/opencart/admin/config.php

# Prepare .htaccess for SEO URLs
sudo mv /var/www/opencart/htaccess.txt /var/www/opencart/.htaccess

# Ownership/permissions
sudo chown -R www-data:www-data /var/www/opencart
sudo find /var/www/opencart -type d -exec chmod 755 {} \;
sudo find /var/www/opencart -type f -exec chmod 644 {} \;

# Allow installer to write config files during setup (we'll lock down later)
sudo chmod 664 /var/www/opencart/config.php /var/www/opencart/admin/config.php
</code></pre>


<h2 class="wp-block-heading">Step 5 — Configure Apache Virtual Host</h2>



<p class="wp-block-paragraph">Replace <code>example.com</code> with your domain.</p>


<pre><code>sudo tee /etc/apache2/sites-available/opencart.conf >/dev/null <<'EOF'
&lt;VirtualHost *:80&gt;
  ServerName example.com
  ServerAlias www.example.com
  DocumentRoot /var/www/opencart

  &lt;Directory /var/www/opencart&gt;
    AllowOverride All
    Require all granted
  &lt;/Directory&gt;

  ErrorLog ${APACHE_LOG_DIR}/oc_error.log
  CustomLog ${APACHE_LOG_DIR}/oc_access.log combined
&lt;/VirtualHost&gt;
EOF

sudo a2ensite opencart.conf
sudo apache2ctl configtest &#038;&#038; sudo systemctl reload apache2
</code></pre>


<h2 class="wp-block-heading">Step 6 — Enable HTTPS with Let’s Encrypt</h2>


<pre><code>sudo apt -y install certbot python3-certbot-apache
sudo certbot --apache -d example.com -d www.example.com --redirect -m you@example.com --agree-tos -n
</code></pre>


<h2 class="wp-block-heading">Step 7 — Run the Web Installer</h2>



<ul class="wp-block-list">
  <li>Open <code>https://example.com</code> and follow the installer.</li>
  <li>Database: <code>ocdb</code>, User: <code>ocuser</code>, Password: <code>ChangeThisStrongPassword!</code>, Host: <code>localhost</code>.</li>
  <li>Admin path: keep the suggested unique URL for security.</li>
</ul>



<p class="wp-block-paragraph"><em>After installation</em>, tighten configs and (optionally) move storage outside the web root:</p>


<pre><code># Lock down configs
sudo chmod 644 /var/www/opencart/config.php /var/www/opencart/admin/config.php

# (Optional) Move storage folder outside the web root for security
sudo mkdir -p /var/www/oc-storage
sudo rsync -a /var/www/opencart/system/storage/ /var/www/oc-storage/
# Update both config files so DIR_STORAGE points to /var/www/oc-storage/
sudo sed -i "s#'DIR_STORAGE'.*#'DIR_STORAGE', '/var/www/oc-storage/' );#g" /var/www/opencart/config.php
sudo sed -i "s#'DIR_STORAGE'.*#'DIR_STORAGE', '/var/www/oc-storage/' );#g" /var/www/opencart/admin/config.php
</code></pre>


<h2 class="wp-block-heading">Step 8 — Turn On SEO-Friendly URLs</h2>



<ul class="wp-block-list">
  <li>In Admin: <strong>System → Settings → Your Store → Server</strong> → enable <strong>Use SEO URLs</strong>.</li>
  <li>You already renamed <code>htaccess.txt</code> to <code>.htaccess</code> and enabled <code>mod_rewrite</code> in earlier steps.</li>
</ul>



<h2 class="wp-block-heading">Step 9 — Sample Data &amp; Theme Basics</h2>



<ul class="wp-block-list">
  <li><strong>Sample data:</strong> OpenCart ships with demo products/categories on fresh installs. Replace them under <em>Catalog → Products/Categories</em> as you build your store.</li>
  <li><strong>Themes:</strong> Go to <em>Extensions → Extensions</em>, choose “Themes”, edit <em>Your Store</em>, select a theme (or install one via <em>Extensions → Installer</em>), then enable and save.</li>
</ul>



<h2 class="wp-block-heading">Step 10 — Email &amp; Payments</h2>



<ul class="wp-block-list">
  <li><strong>Order email:</strong> In <em>System → Settings → Your Store → Mail</em>, choose SMTP and enter your provider’s host, port, encryption, username, and password; send a test email.</li>
  <li><strong>Gateways:</strong> In <em>Extensions → Extensions</em> (choose “Payments”), install Stripe/PayPal and connect your merchant account.</li>
</ul>



<h2 class="wp-block-heading">Optional: Quick Backup Script</h2>


<pre><code>sudo mkdir -p /opt/oc-backups
sudo tee /opt/oc-backups/backup.sh >/dev/null <<'EOF'
#!/usr/bin/env bash
set -e
TS=$(date +%F-%H%M)
SITE_ROOT="/var/www/opencart"
DB_NAME="ocdb"
DB_USER="ocuser"
DB_PASS="ChangeThisStrongPassword!"

mkdir -p /opt/oc-backups/${TS}
mysqldump -u ${DB_USER} -p${DB_PASS} ${DB_NAME} | gzip > /opt/oc-backups/${TS}/db.sql.gz
tar -czf /opt/oc-backups/${TS}/site-files.tgz -C "${SITE_ROOT}" .
find /opt/oc-backups -maxdepth 1 -type d -mtime +14 -exec rm -rf {} \; 2>/dev/null || true
EOF

sudo chmod +x /opt/oc-backups/backup.sh
echo "30 2 * * * root /opt/oc-backups/backup.sh" | sudo tee /etc/cron.d/oc-backup >/dev/null
</code></pre>


<h2 class="wp-block-heading">Troubleshooting</h2>



<ul class="wp-block-list">
  <li><strong>Installer fails requirements:</strong> Confirm PHP extensions (curl, zip, zlib, gd, mbstring, intl) are installed.</li>
  <li><strong>SEO URLs not working:</strong> Ensure <code>mod_rewrite</code> is enabled, your vHost allows <code>AllowOverride All</code>, and <code>.htaccess</code> exists in the web root.</li>
  <li><strong>Permission errors:</strong> Temporarily set <code>config.php</code> files to <code>664</code> for installation, then restore to <code>644</code>.</li>
  <li><strong>SSL issues:</strong> Verify DNS points to your server before running Certbot; re-run with <code>--apache</code> if needed.</li>
</ul>



<p class="wp-block-paragraph">Want a faster start? Choose an instant, low-cost <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium dedicated server</a> and be online today.</p>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">Your OpenCart store is now live with HTTPS, SEO URLs, and a theme foundation—ready for products, payments, and growth on ServerStadium. For more help or information about ServerStadium services, visit our <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">knowledge base</a> or the <a href="https://serverstadium.com/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium website</a>.</p>

<p>The post <a href="https://serverstadium.com/knowledge-base/opencart-on-dedicated-server-quickstart/">Install OpenCart on a ServerStadium Dedicated Server</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Starting an Online Store with WooCommerce on a Dedicated Server</title>
		<link>https://serverstadium.com/knowledge-base/woocommerce-on-dedicated-server-beginners/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Tue, 12 Aug 2025 17:42:39 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=12185</guid>

					<description><![CDATA[<p>Introduction This guide walks you through launching a WooCommerce-powered store on a ServerStadium dedicated server (or ServerStadium VM) running Ubuntu 24.04. You’ll install WordPress, add WooCommerce, enable SSL with Let’s Encrypt, configure payments and email, and apply easy performance tweaks—perfect for small businesses that need a fast, affordable, and reliable storefront. Prerequisites A ServerStadium dedicated&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/woocommerce-on-dedicated-server-beginners/">Starting an Online Store with WooCommerce on a Dedicated Server</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Introduction</h2>



<p class="wp-block-paragraph">This guide walks you through launching a WooCommerce-powered store on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> (or <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium VM</a>) running Ubuntu 24.04. You’ll install WordPress, add WooCommerce, enable SSL with Let’s Encrypt, configure payments and email, and apply easy performance tweaks—perfect for small businesses that need a fast, affordable, and reliable storefront.</p>



<h2 class="wp-block-heading">Prerequisites</h2>



<ul class="wp-block-list">
  <li>A <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> (Ubuntu 24.04 recommended) and a domain pointed to your server’s IP.</li>
  <li>SSH access with a sudo-capable user.</li>
  <li>An email address for Let’s Encrypt notifications, and an SMTP provider (or WordPress SMTP plugin) for order emails.</li>
</ul>



<h2 class="wp-block-heading">Option A: LAMP (Apache) Quick Start</h2>



<p class="wp-block-paragraph"><strong>1) Install packages</strong></p>


<pre><code>sudo apt update && sudo apt -y upgrade
sudo apt -y install apache2 mysql-server \
  php php-fpm php-mysql php-curl php-xml php-gd php-zip php-mbstring php-intl php-bcmath \
  unzip curl
sudo a2enmod rewrite
sudo systemctl enable --now apache2 mysql
</code></pre>


<p class="wp-block-paragraph"><strong>2) Secure MySQL and create the store database</strong></p>


<pre><code>sudo mysql_secure_installation
sudo mysql -e "CREATE DATABASE shopdb DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;"
sudo mysql -e "CREATE USER 'shopuser'@'localhost' IDENTIFIED BY 'ChangeThisStrongPassword!';"
sudo mysql -e "GRANT ALL PRIVILEGES ON shopdb.* TO 'shopuser'@'localhost'; FLUSH PRIVILEGES;"
</code></pre>


<p class="wp-block-paragraph"><strong>3) Download and place WordPress</strong></p>


<pre><code>cd /tmp
curl -LO https://wordpress.org/latest.tar.gz
tar -xzf latest.tar.gz
sudo rsync -a wordpress/ /var/www/html/
sudo chown -R www-data:www-data /var/www/html
sudo find /var/www/html -type d -exec chmod 755 {} \;
sudo find /var/www/html -type f -exec chmod 644 {} \;
</code></pre>


<p class="wp-block-paragraph"><strong>4) Apache vHost (replace <code>example.com</code>)</strong></p>


<pre><code>sudo tee /etc/apache2/sites-available/wordpress.conf >/dev/null <<'EOF'
&lt;VirtualHost *:80&gt;
    ServerName example.com
    ServerAlias www.example.com
    DocumentRoot /var/www/html
    &lt;Directory /var/www/html&gt;
        AllowOverride All
        Require all granted
    &lt;/Directory&gt;
    ErrorLog ${APACHE_LOG_DIR}/wp_error.log
    CustomLog ${APACHE_LOG_DIR}/wp_access.log combined
&lt;/VirtualHost&gt;
EOF

sudo a2ensite wordpress.conf
sudo systemctl reload apache2
</code></pre>


<p class="wp-block-paragraph"><strong>5) Configure WordPress</strong></p>


<pre><code>cd /var/www/html
cp wp-config-sample.php wp-config.php
sed -i "s/database_name_here/shopdb/; s/username_here/shopuser/; s/password_here/ChangeThisStrongPassword!/" wp-config.php
curl -s https://api.wordpress.org/secret-key/1.1/salt/ | sudo tee -a wp-config.php >/dev/null
sudo chown www-data:www-data wp-config.php
</code></pre>


<p class="wp-block-paragraph"><strong>6) Enable HTTPS (Let’s Encrypt)</strong></p>


<pre><code>sudo apt -y install certbot python3-certbot-apache
sudo certbot --apache -d example.com -d www.example.com --redirect -m you@example.com --agree-tos -n
</code></pre>


<h2 class="wp-block-heading">Option B: LEMP (Nginx) Quick Start</h2>



<p class="wp-block-paragraph"><strong>1) Install packages</strong></p>


<pre><code>sudo apt update
sudo apt -y install nginx mysql-server \
  php-fpm php-mysql php-curl php-xml php-gd php-zip php-mbstring php-intl php-bcmath \
  unzip curl
sudo systemctl enable --now nginx mysql
</code></pre>


<p class="wp-block-paragraph"><strong>2) Create database</strong> (reuse the <code>mysql</code> commands from LAMP step 2).</p>



<p class="wp-block-paragraph"><strong>3) Install WordPress files</strong></p>


<pre><code>cd /tmp
curl -LO https://wordpress.org/latest.tar.gz
tar -xzf latest.tar.gz
sudo mkdir -p /var/www/wordpress
sudo rsync -a wordpress/ /var/www/wordpress/
sudo chown -R www-data:www-data /var/www/wordpress
</code></pre>


<p class="wp-block-paragraph"><strong>4) Nginx server block (replace <code>example.com</code>)</strong></p>


<pre><code>sudo tee /etc/nginx/sites-available/wordpress >/dev/null <<'EOF'
server {
    listen 80;
    server_name example.com www.example.com;
    root /var/www/wordpress;
    index index.php index.html;

    location / {
        try_files $uri $uri/ /index.php?$args;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/run/php/php-fpm.sock;
    }

    location ~* \.(png|jpg|jpeg|gif|ico|css|js|svg|webp)$ {
        expires max;
        access_log off;
    }
}
EOF

sudo ln -s /etc/nginx/sites-available/wordpress /etc/nginx/sites-enabled/wordpress
sudo nginx -t &#038;&#038; sudo systemctl reload nginx
</code></pre>


<p class="wp-block-paragraph"><strong>5) Configure WordPress</strong></p>


<pre><code>cd /var/www/wordpress
cp wp-config-sample.php wp-config.php
sed -i "s/database_name_here/shopdb/; s/username_here/shopuser/; s/password_here/ChangeThisStrongPassword!/" wp-config.php
curl -s https://api.wordpress.org/secret-key/1.1/salt/ | sudo tee -a wp-config.php >/dev/null
sudo chown www-data:www-data wp-config.php
</code></pre>


<p class="wp-block-paragraph"><strong>6) Enable HTTPS (Let’s Encrypt)</strong></p>


<pre><code>sudo apt -y install certbot python3-certbot-nginx
sudo certbot --nginx -d example.com -d www.example.com --redirect -m you@example.com --agree-tos -n
</code></pre>


<h2 class="wp-block-heading">Finish WordPress Setup &amp; Install WooCommerce</h2>



<p class="wp-block-paragraph">Visit <code>https://example.com</code>, complete the WordPress installer, then install WooCommerce. The easiest path is WP-CLI (you can also use the WordPress dashboard).</p>


<pre><code># Install WP-CLI
cd ~
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
php wp-cli.phar --info && chmod +x wp-cli.phar && sudo mv wp-cli.phar /usr/local/bin/wp

# Go to your site root (Apache default shown; for Nginx use /var/www/wordpress)
cd /var/www/html

# Install and activate WooCommerce
sudo -u www-data wp plugin install woocommerce --activate

# Optional: install Stripe gateway (recommended)
sudo -u www-data wp plugin install woocommerce-gateway-stripe --activate

# Optional: install an SMTP plugin for reliable order emails
sudo -u www-data wp plugin install wp-mail-smtp --activate
</code></pre>


<p class="wp-block-paragraph">In the WordPress dashboard go to <em>WooCommerce → Settings</em> and run the setup wizard (store address, currency, shipping). Then open <em>WooCommerce → Settings → Payments</em> to enable Stripe (or your preferred gateway) and connect your account. Configure <em>WP Mail SMTP</em> (or your SMTP plugin) with your provider’s credentials so order receipts and password resets are delivered reliably.</p>



<h2 class="wp-block-heading">Essential Store Tweaks</h2>



<ul class="wp-block-list">
  <li><strong>Permalinks:</strong> Go to <em>Settings → Permalinks</em> and choose “Post name,” then click <em>Save</em>.</li>
  <li><strong>Image sizes:</strong> In <em>Settings → Media</em>, set reasonable sizes (e.g., large 1200px). Consider a compression plugin for faster product pages.</li>
  <li><strong>PHP memory limit:</strong> For medium stores, consider raising to 256M:
    <br><code>echo "memory_limit = 256M" | sudo tee /etc/php/*/apache2/conf.d/99-memory.ini /etc/php/*/fpm/conf.d/99-memory.ini</code>
    <br><code>sudo systemctl reload apache2 || sudo systemctl reload php*-fpm</code>
  </li>
  <li><strong>Caching:</strong> Simple page caching helps. Example (optional) via WP-CLI:
    <br><code>sudo -u www-data wp plugin install cache-enabler --activate</code>
  </li>
  <li><strong>Firewall:</strong> Allow web/SSH traffic:
    <br><code>sudo ufw allow OpenSSH && sudo ufw allow 80 && sudo ufw allow 443 && sudo ufw enable</code>
  </li>
</ul>



<h2 class="wp-block-heading">Backups (Quick Script)</h2>



<p class="wp-block-paragraph">Back up files and database nightly. Adjust paths if you used Nginx root (<code>/var/www/wordpress</code>).</p>


<pre><code>sudo mkdir -p /opt/shop-backups
sudo tee /opt/shop-backups/backup.sh >/dev/null <<'EOF'
#!/usr/bin/env bash
set -e
TS=$(date +%F-%H%M)
SITE_ROOT="/var/www/html"   # or /var/www/wordpress
DB_NAME="shopdb"
DB_USER="shopuser"
DB_PASS="ChangeThisStrongPassword!"

mkdir -p /opt/shop-backups/${TS}
mysqldump -u ${DB_USER} -p${DB_PASS} ${DB_NAME} | gzip > /opt/shop-backups/${TS}/db.sql.gz
tar -czf /opt/shop-backups/${TS}/wp-files.tgz -C "${SITE_ROOT}" .
# Keep 14 days
find /opt/shop-backups -maxdepth 1 -type d -mtime +14 -exec rm -rf {} \; 2>/dev/null || true
EOF

sudo chmod +x /opt/shop-backups/backup.sh
echo "0 2 * * * root /opt/shop-backups/backup.sh" | sudo tee /etc/cron.d/shop-backup >/dev/null
</code></pre>


<h2 class="wp-block-heading">Troubleshooting</h2>



<ul class="wp-block-list">
  <li><strong>SSL issues:</strong> Make sure DNS A/AAAA records point to your server before running Certbot. Re-run with <code>--apache</code> or <code>--nginx</code>.</li>
  <li><strong>Permalinks not working (Apache):</strong> Confirm <code>AllowOverride All</code> is set and <code>a2enmod rewrite</code> is enabled; reload Apache.</li>
  <li><strong>Orders not emailing:</strong> Verify SMTP plugin settings; check <em>WooCommerce → Status → Logs</em>.</li>
  <li><strong>502/504 with Nginx:</strong> Check PHP-FPM: <code>systemctl status php*-fpm</code>; increase <code>client_max_body_size</code> for large uploads if needed.</li>
</ul>



<p class="wp-block-paragraph">Ready to sell? Spin up a low-cost, instant <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> and launch today.</p>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">With WordPress and WooCommerce configured on ServerStadium, you’ve got a fast and dependable foundation for your online store—complete with SSL, payments, email, and backups. For more help or information about ServerStadium services, visit our <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">knowledge base</a> or the <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium website</a>.</p>

<p>The post <a href="https://serverstadium.com/knowledge-base/woocommerce-on-dedicated-server-beginners/">Starting an Online Store with WooCommerce on a Dedicated Server</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>One-Click WordPress on Ubuntu 24.04 for Small Business Sites</title>
		<link>https://serverstadium.com/knowledge-base/simple-wordpress-ubuntu-24-04-dedicated-servers/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Tue, 12 Aug 2025 17:32:21 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=12181</guid>

					<description><![CDATA[<p>Introduction This guide will walk you through installing WordPress on a ServerStadium VM or a ServerStadium dedicated server running Ubuntu 24.04. We’ll cover both Apache (LAMP) and Nginx (LEMP), free SSL with Let’s Encrypt, and simple backup &#38; update routines—everything a small business needs to get online quickly with great performance. Prerequisites A ServerStadium VM&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/simple-wordpress-ubuntu-24-04-dedicated-servers/">One-Click WordPress on Ubuntu 24.04 for Small Business Sites</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Introduction</h2>



<p class="wp-block-paragraph">This guide will walk you through installing WordPress on a <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium VM</a> or a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> running Ubuntu 24.04. We’ll cover both Apache (LAMP) and Nginx (LEMP), free SSL with Let’s Encrypt, and simple backup &amp; update routines—everything a small business needs to get online quickly with great performance.</p>



<h2 class="wp-block-heading">Prerequisites</h2>



<ul class="wp-block-list">
  <li>A <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium VM</a> or <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">dedicated server</a> with Ubuntu 24.04 and a domain pointed to your server’s IP.</li>
  <li>SSH access with a sudo-capable user.</li>
  <li>An email address for Let’s Encrypt notifications (recommended).</li>
</ul>



<h2 class="wp-block-heading">Option A: LAMP (Apache) Quick Install</h2>



<p class="wp-block-paragraph">This path uses Apache + PHP + MySQL and enables HTTPS via the Certbot Apache plugin.</p>



<p class="wp-block-paragraph"><strong>1) Update and install packages</strong></p>


<pre><code>sudo apt update && sudo apt -y upgrade
sudo apt -y install apache2 mysql-server php php-mysql php-curl php-xml php-gd php-zip php-mbstring php-intl unzip
sudo a2enmod rewrite
sudo systemctl enable --now apache2 mysql
</code></pre>


<p class="wp-block-paragraph"><strong>2) Secure MySQL &amp; create the WordPress database</strong></p>


<pre><code>sudo mysql_secure_installation
sudo mysql -e "CREATE DATABASE wpdb DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;"
sudo mysql -e "CREATE USER 'wpuser'@'localhost' IDENTIFIED BY 'ChangeThisStrongPassword!';"
sudo mysql -e "GRANT ALL PRIVILEGES ON wpdb.* TO 'wpuser'@'localhost'; FLUSH PRIVILEGES;"
</code></pre>


<p class="wp-block-paragraph"><strong>3) Download &amp; place WordPress</strong></p>


<pre><code>cd /tmp
curl -LO https://wordpress.org/latest.tar.gz
tar -xzf latest.tar.gz
sudo rsync -a wordpress/ /var/www/html/
sudo chown -R www-data:www-data /var/www/html
sudo find /var/www/html -type d -exec chmod 755 {} \;
sudo find /var/www/html -type f -exec chmod 644 {} \;
</code></pre>


<p class="wp-block-paragraph"><strong>4) Configure Apache vHost</strong> (replace <code>example.com</code> with your domain)</p>


<pre><code>sudo tee /etc/apache2/sites-available/wordpress.conf >/dev/null <<'EOF'
&lt;VirtualHost *:80&gt;
    ServerName example.com
    ServerAlias www.example.com
    DocumentRoot /var/www/html

    &lt;Directory /var/www/html&gt;
        AllowOverride All
        Require all granted
    &lt;/Directory&gt;

    ErrorLog ${APACHE_LOG_DIR}/wp_error.log
    CustomLog ${APACHE_LOG_DIR}/wp_access.log combined
&lt;/VirtualHost&gt;
EOF

sudo a2ensite wordpress.conf
sudo systemctl reload apache2
</code></pre>


<p class="wp-block-paragraph"><strong>5) Create <code>wp-config.php</code> and add secure keys</strong></p>


<pre><code>cd /var/www/html
cp wp-config-sample.php wp-config.php
sed -i "s/database_name_here/wpdb/g; s/username_here/wpuser/g; s/password_here/ChangeThisStrongPassword!/g" wp-config.php
curl -s https://api.wordpress.org/secret-key/1.1/salt/ | sudo tee /tmp/wp.keys >/dev/null
sudo awk 'BEGIN{print "[MARK]"}1' wp-config.php | sed -e "/\[MARK\]/r /tmp/wp.keys" -e "/\[MARK\]/d" | sudo tee wp-config.php.new >/dev/null
sudo mv wp-config.php.new wp-config.php
sudo chown www-data:www-data wp-config.php
</code></pre>


<p class="wp-block-paragraph"><strong>6) Enable HTTPS (Let’s Encrypt)</strong></p>


<pre><code>sudo apt -y install certbot python3-certbot-apache
sudo certbot --apache -d example.com -d www.example.com --redirect -m you@example.com --agree-tos -n
</code></pre>


<h2 class="wp-block-heading">Option B: LEMP (Nginx) Quick Install</h2>



<p class="wp-block-paragraph">Prefer Nginx? Use PHP-FPM + Nginx + MySQL, then secure with Certbot’s Nginx plugin.</p>



<p class="wp-block-paragraph"><strong>1) Install Nginx, PHP-FPM, MySQL</strong></p>


<pre><code>sudo apt update
sudo apt -y install nginx mysql-server php-fpm php-mysql php-curl php-xml php-gd php-zip php-mbstring php-intl unzip
sudo systemctl enable --now nginx mysql
</code></pre>


<p class="wp-block-paragraph"><strong>2) Database (same as LAMP)</strong> — reuse the MySQL commands above to create <code>wpdb</code>/<code>wpuser</code>.</p>



<p class="wp-block-paragraph"><strong>3) Download &amp; set permissions</strong> (same as LAMP), but place WordPress at <code>/var/www/wordpress</code> for clarity:</p>


<pre><code>sudo mkdir -p /var/www/wordpress
sudo rsync -a /tmp/wordpress/ /var/www/wordpress/
sudo chown -R www-data:www-data /var/www/wordpress
</code></pre>


<p class="wp-block-paragraph"><strong>4) Nginx server block</strong> (replace <code>example.com</code>):</p>


<pre><code>sudo tee /etc/nginx/sites-available/wordpress >/dev/null <<'EOF'
server {
    listen 80;
    server_name example.com www.example.com;
    root /var/www/wordpress;

    index index.php index.html;
    location / {
        try_files $uri $uri/ /index.php?$args;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/run/php/php-fpm.sock;
    }

    location ~* \.(png|jpg|jpeg|gif|ico|css|js)$ {
        expires max;
        log_not_found off;
    }
}
EOF

sudo ln -s /etc/nginx/sites-available/wordpress /etc/nginx/sites-enabled/wordpress
sudo nginx -t &#038;&#038; sudo systemctl reload nginx
</code></pre>


<p class="wp-block-paragraph"><strong>5) Create <code>wp-config.php</code> and salts</strong> (same as LAMP, but in <code>/var/www/wordpress</code>):</p>


<pre><code>cd /var/www/wordpress
cp wp-config-sample.php wp-config.php
sed -i "s/database_name_here/wpdb/g; s/username_here/wpuser/g; s/password_here/ChangeThisStrongPassword!/g" wp-config.php
curl -s https://api.wordpress.org/secret-key/1.1/salt/ | sudo tee -a wp-config.php >/dev/null
sudo chown www-data:www-data wp-config.php
</code></pre>


<p class="wp-block-paragraph"><strong>6) Enable HTTPS (Let’s Encrypt)</strong></p>


<pre><code>sudo apt -y install certbot python3-certbot-nginx
sudo certbot --nginx -d example.com -d www.example.com --redirect -m you@example.com --agree-tos -n
</code></pre>


<h2 class="wp-block-heading">Finish Setup in the Browser</h2>



<p class="wp-block-paragraph">Visit <code>https://example.com</code> to complete the WordPress installer (site title, admin user). After logging in, go to <em>Settings → Permalinks</em> and click <em>Save</em> once to ensure pretty URLs work.</p>



<h2 class="wp-block-heading">Performance &amp; Security Basics</h2>



<ul class="wp-block-list">
  <li><strong>Permalinks &amp; rewrites:</strong> Apache needs <code>AllowOverride All</code> and Nginx uses the <code>try_files</code> rule shown above.</li>
  <li><strong>PHP modules:</strong> We installed commonly needed modules (curl, xml, gd, zip, mbstring, intl) for plugin/theme compatibility.</li>
  <li><strong>Auto-renew TLS:</strong> Certbot installs a timer by default. Verify with <code>systemctl status certbot.timer</code>.</li>
  <li><strong>Admin hygiene:</strong> Use strong passwords, enable two-factor for wp-admin, and keep plugins/themes minimal.</li>
</ul>



<h2 class="wp-block-heading">Simple Backups (Files + Database)</h2>



<p class="wp-block-paragraph">Create a quick backup script and schedule it with cron.</p>


<pre><code>sudo mkdir -p /opt/wp-backups
sudo tee /opt/wp-backups/backup.sh >/dev/null <<'EOF'
#!/usr/bin/env bash
set -e
TS=$(date +%F-%H%M)
SITE_ROOT="/var/www/html"   # or /var/www/wordpress for Nginx option
DB_NAME="wpdb"
DB_USER="wpuser"
DB_PASS="ChangeThisStrongPassword!"

mkdir -p /opt/wp-backups/${TS}
mysqldump -u ${DB_USER} -p${DB_PASS} ${DB_NAME} | gzip > /opt/wp-backups/${TS}/db.sql.gz
tar -czf /opt/wp-backups/${TS}/wp-files.tgz -C "${SITE_ROOT}" .
find /opt/wp-backups -type d -mtime +14 -exec rm -rf {} \; 2>/dev/null || true
EOF

sudo chmod +x /opt/wp-backups/backup.sh
echo "0 3 * * * root /opt/wp-backups/backup.sh" | sudo tee /etc/cron.d/wp-backup >/dev/null
</code></pre>


<h2 class="wp-block-heading">Keeping WordPress Updated</h2>



<ul class="wp-block-list">
  <li><strong>Core/plugin/theme updates:</strong> In <em>Dashboard → Updates</em>, apply updates weekly.</li>
  <li><strong>CLI (optional):</strong> Install WP-CLI for scripted updates: <code>curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar && php wp-cli.phar --info</code>.</li>
  <li><strong>Backups first:</strong> Run your backup script before major updates or theme changes.</li>
</ul>



<h2 class="wp-block-heading">One-Click Installer (Optional)</h2>



<p class="wp-block-paragraph">Prefer a single command? This script asks for your domain, email, and stack (LAMP or LEMP), then installs WordPress with HTTPS automatically.</p>


<pre><code>cat <<'SCRIPT' > ~/oneclick-wp.sh
#!/usr/bin/env bash
set -euo pipefail
read -rp "Domain (e.g., example.com): " DOMAIN
read -rp "Email for Let's Encrypt: " EMAIL
read -rp "Stack [lamp|lemp]: " STACK
DB_NAME="wpdb"; DB_USER="wpuser"; DB_PASS="$(tr -dc A-Za-z0-9_@%+ | head -c 20)"

sudo apt update
if [[ "$STACK" == "lamp" ]]; then
  sudo apt -y install apache2 mysql-server php php-mysql php-fpm php-curl php-xml php-gd php-zip php-mbstring php-intl unzip certbot python3-certbot-apache
  sudo a2enmod rewrite
  sudo systemctl enable --now apache2 mysql
  sudo mysql -e "CREATE DATABASE ${DB_NAME} DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;"
  sudo mysql -e "CREATE USER '${DB_USER}'@'localhost' IDENTIFIED BY '${DB_PASS}'; GRANT ALL ON ${DB_NAME}.* TO '${DB_USER}'@'localhost'; FLUSH PRIVILEGES;"
  cd /tmp && curl -LO https://wordpress.org/latest.tar.gz && tar -xzf latest.tar.gz
  sudo rsync -a wordpress/ /var/www/html/
  sudo chown -R www-data:www-data /var/www/html
  sudo tee /etc/apache2/sites-available/wordpress.conf >/dev/null <<EOF
&lt;VirtualHost *:80&gt;
  ServerName ${DOMAIN}
  ServerAlias www.${DOMAIN}
  DocumentRoot /var/www/html
  &lt;Directory /var/www/html&gt;AllowOverride All&lt;/Directory&gt;
&lt;/VirtualHost&gt;
EOF
  sudo a2ensite wordpress.conf &#038;&#038; sudo systemctl reload apache2
  cd /var/www/html &#038;&#038; cp wp-config-sample.php wp-config.php
  sudo sed -i "s/database_name_here/${DB_NAME}/; s/username_here/${DB_USER}/; s/password_here/${DB_PASS}/" wp-config.php
  curl -s https://api.wordpress.org/secret-key/1.1/salt/ | sudo tee -a wp-config.php >/dev/null
  sudo certbot --apache -d "${DOMAIN}" -d "www.${DOMAIN}" --redirect -m "${EMAIL}" --agree-tos -n
else
  sudo apt -y install nginx mysql-server php-fpm php-mysql php-curl php-xml php-gd php-zip php-mbstring php-intl unzip certbot python3-certbot-nginx
  sudo systemctl enable --now nginx mysql
  sudo mysql -e "CREATE DATABASE ${DB_NAME} DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;"
  sudo mysql -e "CREATE USER '${DB_USER}'@'localhost' IDENTIFIED BY '${DB_PASS}'; GRANT ALL ON ${DB_NAME}.* TO '${DB_USER}'@'localhost'; FLUSH PRIVILEGES;"
  cd /tmp && curl -LO https://wordpress.org/latest.tar.gz && tar -xzf latest.tar.gz
  sudo mkdir -p /var/www/wordpress && sudo rsync -a wordpress/ /var/www/wordpress/
  sudo chown -R www-data:www-data /var/www/wordpress
  sudo tee /etc/nginx/sites-available/wordpress >/dev/null <<EOF
server {
  listen 80;
  server_name ${DOMAIN} www.${DOMAIN};
  root /var/www/wordpress;
  index index.php index.html;
  location / { try_files \$uri \$uri/ /index.php?\$args; }
  location ~ \.php$ { include snippets/fastcgi-php.conf; fastcgi_pass unix:/run/php/php-fpm.sock; }
}
EOF
  sudo ln -s /etc/nginx/sites-available/wordpress /etc/nginx/sites-enabled/wordpress
  sudo nginx -t &#038;&#038; sudo systemctl reload nginx
  cd /var/www/wordpress &#038;&#038; cp wp-config-sample.php wp-config.php
  sudo sed -i "s/database_name_here/${DB_NAME}/; s/username_here/${DB_USER}/; s/password_here/${DB_PASS}/" wp-config.php
  curl -s https://api.wordpress.org/secret-key/1.1/salt/ | sudo tee -a wp-config.php >/dev/null
  sudo certbot --nginx -d "${DOMAIN}" -d "www.${DOMAIN}" --redirect -m "${EMAIL}" --agree-tos -n
fi
echo "DB: ${DB_NAME}  USER: ${DB_USER}  PASS: ${DB_PASS}"
echo "Open https://${DOMAIN} to finish WordPress setup."
SCRIPT

chmod +x ~/oneclick-wp.sh
bash ~/oneclick-wp.sh
</code></pre>


<h2 class="wp-block-heading">Troubleshooting</h2>



<ul class="wp-block-list">
  <li><strong>White page / 502 errors:</strong> Check PHP-FPM/Apache status: <code>systemctl status php*-fpm apache2 nginx</code>.</li>
  <li><strong>Permalinks not working (Apache):</strong> Confirm <code>AllowOverride All</code> and that <code>mod_rewrite</code> is enabled.</li>
  <li><strong>SSL issuance fails:</strong> Confirm DNS A/AAAA records point to your server and re-run Certbot with <code>--apache</code> or <code>--nginx</code>.</li>
</ul>



<p class="wp-block-paragraph">Need a faster start? Choose a low-cost, instant <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium dedicated server</a> and be online today.</p>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">That’s it—your small business WordPress site is live with modern PHP, a secure database, and free SSL on high-performance ServerStadium hardware. For more help or information about ServerStadium services, visit our <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">knowledge base</a> or the <a href="https://serverstadium.com/?utm_source=kb&amp;utm_medium=article&amp;utm_campaign=dedicated_server">ServerStadium website</a>.</p>

<p>The post <a href="https://serverstadium.com/knowledge-base/simple-wordpress-ubuntu-24-04-dedicated-servers/">One-Click WordPress on Ubuntu 24.04 for Small Business Sites</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Hosting Chamilo Learning Management System on ServerStadium Dedicated Servers</title>
		<link>https://serverstadium.com/knowledge-base/hosting-chamilo-learning-management-system-dedicated-servers/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Mon, 31 Mar 2025 16:14:05 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=12173</guid>

					<description><![CDATA[<p>Introduction This guide explains how to host Chamilo, an open-source Learning Management System (LMS), on a ServerStadium dedicated server. Chamilo provides a comprehensive platform for online education and training, making it an ideal solution for schools, businesses, and organizations. By leveraging ServerStadium’s high-performance hosting, you can deploy a scalable and secure Chamilo environment to support&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/hosting-chamilo-learning-management-system-dedicated-servers/">Hosting Chamilo Learning Management System on ServerStadium Dedicated Servers</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Introduction</h2>



<p class="wp-block-paragraph">This guide explains how to host Chamilo, an open-source Learning Management System (LMS), on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a>. Chamilo provides a comprehensive platform for online education and training, making it an ideal solution for schools, businesses, and organizations. By leveraging ServerStadium’s high-performance hosting, you can deploy a scalable and secure Chamilo environment to support effective e-learning experiences.</p>



<h2 class="wp-block-heading">Prerequisites</h2>



<p class="wp-block-paragraph">Before you begin, ensure you have the following:</p>



<ul class="wp-block-list">
  
  <li>A <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> running Ubuntu (or a similar Linux distribution).</li>
  
  
  <li>Basic command line knowledge and sudo privileges.</li>
  
  
  <li>A working LAMP stack (Apache, MySQL/MariaDB, and PHP) or the ability to install these components.</li>
  
  
  <li>Familiarity with Chamilo LMS installation and basic PHP web application concepts.</li>
  
</ul>



<h2 class="wp-block-heading">Deployment Steps</h2>



<h3 class="wp-block-heading">1. Update Your System</h3>



<p class="wp-block-paragraph">Begin by updating your system packages to ensure you have the latest updates and security patches:</p>


<pre><code>sudo apt-get update && sudo apt-get upgrade -y</code></pre>


<h3 class="wp-block-heading">2. Install the LAMP Stack</h3>



<p class="wp-block-paragraph">If you haven’t already set up a LAMP environment, install Apache, MySQL, and PHP with the following command:</p>


<pre><code>sudo apt-get install apache2 mysql-server php php-mysql php-xml php-json -y</code></pre>


<h3 class="wp-block-heading">3. Download and Extract Chamilo</h3>



<p class="wp-block-paragraph">Navigate to your web root directory (typically <code>/var/www/html</code>) and download the latest stable version of Chamilo from GitHub:</p>


<pre><code>cd /var/www/html
wget https://github.com/chamilo/chamilo-lms/releases/download/v1.11.28/chamilo-1.11.28.tar.gz -O chamilo.tar.gz</code></pre>


<p class="wp-block-paragraph">Extract the downloaded archive and rename the directory:</p>


<pre><code>tar -xzvf chamilo.tar.gz
mv chamilo-1.11.28 chamilo</code></pre>


<p class="wp-block-paragraph">Set proper permissions for the Chamilo directory so that the web server can access the files:</p>


<pre><code>sudo chown -R www-data:www-data /var/www/html/chamilo</code></pre>


<h3 class="wp-block-heading">4. Create the Chamilo Database</h3>



<p class="wp-block-paragraph">Create a new MySQL database and user for Chamilo. Access MySQL and run the following commands:</p>


<pre><code>sudo mysql -u root -p
CREATE DATABASE chamilo CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'chamilo_user'@'localhost' IDENTIFIED BY 'YourStrongPassword';
GRANT ALL PRIVILEGES ON chamilo.* TO 'chamilo_user'@'localhost';
FLUSH PRIVILEGES;
EXIT;</code></pre>


<p class="wp-block-paragraph">Replace <code>YourStrongPassword</code> with a secure password.</p>



<h3 class="wp-block-heading">5. Configure Apache for Chamilo</h3>



<p class="wp-block-paragraph">Create a new Apache virtual host configuration for Chamilo:</p>


<pre><code>sudo nano /etc/apache2/sites-available/chamilo.conf</code></pre>


<p class="wp-block-paragraph">Add the following configuration (adjust <code>ServerName</code> and <code>DocumentRoot</code> as needed):</p>


<pre><code>&lt;VirtualHost *:80&gt;
    ServerAdmin admin@yourdomain.com
    ServerName yourdomain.com
    DocumentRoot /var/www/html/chamilo

    &lt;Directory /var/www/html/chamilo&gt;
        Options FollowSymLinks
        AllowOverride All
        Require all granted
    &lt;/Directory&gt;

    ErrorLog ${APACHE_LOG_DIR}/chamilo_error.log
    CustomLog ${APACHE_LOG_DIR}/chamilo_access.log combined
&lt;/VirtualHost&gt;</code></pre>


<p class="wp-block-paragraph">Enable the new site and the Apache rewrite module, then reload Apache:</p>


<pre><code>sudo a2ensite chamilo.conf
sudo a2enmod rewrite
sudo systemctl reload apache2</code></pre>


<h3 class="wp-block-heading">6. Complete Chamilo Installation</h3>



<p class="wp-block-paragraph">Open your web browser and navigate to <code>http://yourdomain.com</code> to access the Chamilo setup page. Follow the on-screen instructions to complete the installation, providing your database details and configuring your Chamilo environment.</p>



<h2 class="wp-block-heading">Post-Deployment Configuration</h2>



<p class="wp-block-paragraph">After installing Chamilo, consider these enhancements to secure and optimize your LMS:</p>


<ul class="wp-block-list">
  
  <li>Configure SSL for secure access using Let&#8217;s Encrypt or another certificate provider.</li>
  
  
  <li>Set up regular backups for your Chamilo data and configuration.</li>
  
  
  <li>Customize Chamilo settings and install additional plugins to enhance functionality and user experience.</li>
  
</ul>
<!-- /wp:post-content -->

<!-- wp:paragraph {"className":""} -->
<p>Hosting your Chamilo LMS on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> ensures a reliable, high-performance, and scalable platform to support your online learning and documentation needs.</p>
<!-- /wp:paragraph -->

<!-- wp:heading {"className":""} -->
<h2 class="wp-block-heading">Troubleshooting</h2>
<!-- /wp:heading -->

<!-- wp:paragraph {"className":""} -->
<p>If you encounter issues during installation or configuration:</p>
<!-- /wp:paragraph -->

<ul class="wp-block-list">
  <!-- wp:list-item -->
  <li>Review Apache error logs located in <code>/var/log/apache2/</code> for any Chamilo-related errors.</li>
  <!-- /wp:list-item -->
  <!-- wp:list-item -->
  <li>Ensure file permissions and ownership are correctly set for the Chamilo directory.</li>
  <!-- /wp:list-item -->
  <!-- wp:list-item -->
  <li>Consult the Chamilo documentation for configuration details and troubleshooting tips.</li>
  <!-- /wp:list-item -->
  <!-- wp:list-item -->
  <li>Refer to our guides in the <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium Knowledge Base</a> for additional assistance.</li>
  <!-- /wp:list-item -->
</ul>
<!-- /wp:list -->

<!-- wp:heading {"className":""} -->
<h2 class="wp-block-heading">Conclusion</h2>
<!-- /wp:heading -->

<!-- wp:paragraph {"className":""} -->
<p>Hosting Chamilo on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> provides a robust and scalable solution for managing your online learning and documentation. By following this guide, you can install and configure a secure Chamilo environment that meets your requirements. For more help or information about ServerStadium services, visit our <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">knowledge base</a> or the <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium website</a>.</p>
<!-- /wp:paragraph -->
<p>The post <a href="https://serverstadium.com/knowledge-base/hosting-chamilo-learning-management-system-dedicated-servers/">Hosting Chamilo Learning Management System on ServerStadium Dedicated Servers</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Hosting DokuWiki for Documentation on ServerStadium Dedicated Servers</title>
		<link>https://serverstadium.com/knowledge-base/hosting-dokuwiki-documentation-dedicated-servers/</link>
		
		<dc:creator><![CDATA[Brian K]]></dc:creator>
		<pubDate>Mon, 31 Mar 2025 16:04:18 +0000</pubDate>
				<guid isPermaLink="false">https://serverstadium.com/?post_type=epkb_post_type_1&#038;p=12171</guid>

					<description><![CDATA[<p>Introduction This tutorial explains how to host DokuWiki – a lightweight, open-source wiki designed for documentation – on a ServerStadium dedicated server. With DokuWiki, you can easily manage and collaborate on documentation, and our high-performance dedicated servers provide a robust platform to support your wiki environment. Prerequisites Before you begin, ensure you have the following:&#8230;</p>
<p>The post <a href="https://serverstadium.com/knowledge-base/hosting-dokuwiki-documentation-dedicated-servers/">Hosting DokuWiki for Documentation on ServerStadium Dedicated Servers</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Introduction</h2>



<p class="wp-block-paragraph">This tutorial explains how to host DokuWiki – a lightweight, open-source wiki designed for documentation – on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a>. With DokuWiki, you can easily manage and collaborate on documentation, and our high-performance dedicated servers provide a robust platform to support your wiki environment.</p>



<h2 class="wp-block-heading">Prerequisites</h2>



<p class="wp-block-paragraph">Before you begin, ensure you have the following:</p>



<ul class="wp-block-list">
  
  <li>A <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> running Ubuntu (or a similar Linux distribution).</li>
  
  
  <li>Basic command line knowledge and sudo privileges.</li>
  
  
  <li>A working LAMP stack (Apache, MySQL/MariaDB, and PHP) or the ability to install these components.</li>
  
  
  <li>Familiarity with PHP and basic web server configuration.</li>
  
</ul>



<h2 class="wp-block-heading">Deployment Steps</h2>



<h3 class="wp-block-heading">1. Update Your System</h3>



<p class="wp-block-paragraph">Start by updating your system packages to ensure you have the latest updates and security patches:</p>


<pre><code>sudo apt-get update && sudo apt-get upgrade -y</code></pre>


<h3 class="wp-block-heading">2. Install Apache, PHP, and Other Dependencies</h3>



<p class="wp-block-paragraph">If not already installed, set up the LAMP stack. For example, to install Apache and PHP:</p>


<pre><code>sudo apt-get install apache2 php php-xml php-json -y</code></pre>


<h3 class="wp-block-heading">3. Download and Install DokuWiki</h3>



<p class="wp-block-paragraph">Navigate to your web root directory (e.g., <code>/var/www/html</code>) and download the latest stable version of DokuWiki:</p>


<pre><code>cd /var/www/html
wget https://download.dokuwiki.org/src/dokuwiki/dokuwiki-stable.tgz -O dokuwiki.tgz</code></pre>


<p class="wp-block-paragraph">Extract the archive and rename the directory:</p>


<pre><code>tar -xzvf dokuwiki.tgz
mv dokuwiki-* dokuwiki</code></pre>


<p class="wp-block-paragraph">Set proper permissions so that the web server can access the files:</p>


<pre><code>sudo chown -R www-data:www-data /var/www/html/dokuwiki</code></pre>


<h3 class="wp-block-heading">4. Configure Apache for DokuWiki</h3>



<p class="wp-block-paragraph">Create a new Apache virtual host configuration for DokuWiki:</p>


<pre><code>sudo nano /etc/apache2/sites-available/dokuwiki.conf</code></pre>


<p class="wp-block-paragraph">Add the following configuration (adjust <code>ServerName</code> and <code>DocumentRoot</code> as needed):</p>


<pre><code>&lt;VirtualHost *:80&gt;
    ServerAdmin admin@yourdomain.com
    ServerName yourdomain.com
    DocumentRoot /var/www/html/dokuwiki

    &lt;Directory /var/www/html/dokuwiki&gt;
        Options FollowSymLinks
        AllowOverride All
        Require all granted
    &lt;/Directory&gt;

    ErrorLog ${APACHE_LOG_DIR}/dokuwiki_error.log
    CustomLog ${APACHE_LOG_DIR}/dokuwiki_access.log combined
&lt;/VirtualHost&gt;</code></pre>


<p class="wp-block-paragraph">Enable the new site and the Apache rewrite module, then reload Apache:</p>


<pre><code>sudo a2ensite dokuwiki.conf
sudo a2enmod rewrite
sudo systemctl reload apache2</code></pre>


<h3 class="wp-block-heading">5. Complete DokuWiki Setup</h3>



<p class="wp-block-paragraph">Open your web browser and navigate to <code>http://yourdomain.com</code> to access the DokuWiki setup page. Follow the on-screen instructions to complete the installation and initial configuration of your wiki.</p>



<h2 class="wp-block-heading">Post-Deployment Configuration</h2>



<p class="wp-block-paragraph">After installing DokuWiki, consider these enhancements to secure and optimize your documentation environment:</p>


<ul class="wp-block-list">
  
  <li>Configure SSL to secure your site using Let&#8217;s Encrypt or another certificate provider.</li>
  
  
  <li>Set up regular backups for your wiki data.</li>
  
  
  <li>Adjust DokuWiki settings and plugins to suit your documentation needs.</li>
  
</ul>
<!-- /wp:post-content -->

<!-- wp:paragraph {"className":""} -->
<p>Hosting your DokuWiki on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> ensures a high-performance, scalable environment for your documentation and collaboration needs.</p>
<!-- /wp:paragraph -->

<!-- wp:heading {"className":""} -->
<h2 class="wp-block-heading">Troubleshooting</h2>
<!-- /wp:heading -->

<!-- wp:paragraph {"className":""} -->
<p>If you encounter issues during installation or configuration:</p>
<!-- /wp:paragraph -->

<ul class="wp-block-list">
  <!-- wp:list-item -->
  <li>Review Apache error logs located in <code>/var/log/apache2/</code> for any errors related to DokuWiki.</li>
  <!-- /wp:list-item -->
  <!-- wp:list-item -->
  <li>Ensure file permissions and ownership are correctly set for the DokuWiki directory.</li>
  <!-- /wp:list-item -->
  <!-- wp:list-item -->
  <li>Consult the DokuWiki documentation for configuration tips and troubleshooting steps.</li>
  <!-- /wp:list-item -->
  <!-- wp:list-item -->
  <li>Refer to our guides in the <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium Knowledge Base</a> for further assistance.</li>
  <!-- /wp:list-item -->
</ul>
<!-- /wp:list -->

<!-- wp:heading {"className":""} -->
<h2 class="wp-block-heading">Conclusion</h2>
<!-- /wp:heading -->

<!-- wp:paragraph {"className":""} -->
<p>Hosting DokuWiki on a <a href="https://serverstadium.com/dedicated-server/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium dedicated server</a> provides a robust and scalable solution for managing your documentation. By following this guide, you can install and configure a secure DokuWiki environment that meets your collaboration and documentation needs. For more help or information about ServerStadium services, visit our <a href="https://serverstadium.com/knowledge-base/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">knowledge base</a> or the <a href="https://serverstadium.com/?utm_source=kb&#038;utm_medium=article&#038;utm_campaign=dedicated_server">ServerStadium website</a>.</p>
<!-- /wp:paragraph -->
<p>The post <a href="https://serverstadium.com/knowledge-base/hosting-dokuwiki-documentation-dedicated-servers/">Hosting DokuWiki for Documentation on ServerStadium Dedicated Servers</a> appeared first on <a href="https://serverstadium.com">ServerStadium</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
