Files
SkyArtShop/VERIFY_SITE.md
Local Server 61929a5daf updateweb
2025-12-14 01:54:40 -06:00

2.5 KiB

How to Verify You're Seeing the New Site

The Issue

You mentioned seeing the "old site" on localhost. Here's what's actually happening:

Current Server Status

  • Port 5000: Your NEW SkyArtShop site (Node.js backend)
  • Port 80: NOTHING running (nginx and apache stopped)

Why You Might See "Old Site"

1. Browser Cache

Your browser is showing cached pages from before cleanup.

Solution:

  • Press Ctrl + Shift + Delete
  • Select "Cached images and files"
  • Clear cache
  • Refresh page (Ctrl + F5 for hard refresh)

2. Wrong URL

You need to use the PORT in the URL.

Wrong: http://localhost/ Correct: http://localhost:5000/

3. Windows Port Forwarding

If you're on Windows accessing the Linux server via RDP, Windows might have port forwarding configured.

How to Test Right Now

Test 1: From Linux Terminal

curl -s http://localhost:5000/ | grep -o "<title>[^<]*</title>"

Should show: <title>Sky Art Shop</title>

Test 2: Check What's Actually Running

./verify-localhost.sh

Should show: Only port 5000 active

Test 3: Check Server Logs

pm2 logs skyartshop --lines 20

Should show: Serving from /media/pts/Website/SkyArtShop/website/

Access Your New Site

Correct URLs

From Windows Browser

If accessing from Windows:

  1. Find your Linux server IP (run ip addr on Linux)
  2. Use: http://YOUR_LINUX_IP:5000/
  3. Example: http://192.168.1.100:5000/

Verification Steps

Run these commands to prove the new site is running:

# Check server status
pm2 status

# Test homepage
curl -s http://localhost:5000/home.html | grep "<title>"

# Test admin
curl -s http://localhost:5000/admin/login.html | grep "<title>"

# Verify no port 80
curl -I http://localhost/ 2>&1 | head -1
# Should show: "Failed to connect" or no response

Quick Fix

# Clear any browser cache, then use the correct URL:
http://localhost:5000/
# NOT
http://localhost/

Summary

Your new cleaned site IS running It's on port 5000, not port 80 Port 80 is disabled (correct for development)

The "old site" you're seeing is probably:

  1. Browser cache showing old pages
  2. Accessing wrong URL (missing :5000)
  3. Windows port forwarding if on remote desktop

Solution: Use http://localhost:5000/ and clear browser cache!