Setting up a subdomain without WordPress

#1
Describe the situation


1. A.com is using WordPress.
You want to use subdomain.A.com as a regular web server without WordPress.

2. Register DNS with your subdomain hosting provider and use the

3. Go to the openlitespeed settings page and click on the
Virtual Hosts > List > Add New

Virtual Host Name = subdomain
Virtual Host Root = /var/www/subdomain/
Config File /usr/local/lsws/conf/vhosts/subdomain/vhconf.conf

Configure and save


Listeners - Default - Port 8088 and create new Virtual Host Mappings
Select Virtual Host = subdomain
Domains = subdomain.A.com,www.subdomain.A.com

Save the settings

Put index.html in /var/www/subdomain/ and select
Access subdomain.A.com but 404 Error





What is wrong?

Thanks for reading.

Translated with www.DeepL.com/Translator (free version)
 
#4
My server settings status.
Is there a problem?

1.png 2.png 3.png 4.png 5.png



/usr/local/lsws/conf/vhosts/subdomain/vhconf.conf


Code:
docRoot                  /var/www/subdomain/

index  {
  useServer               0
  indexFiles              index.php index.html
}

context /phpmyadmin/ {
  location                /var/www/phpmyadmin
  allowBrowse             1
  indexFiles              index.php

  accessControl  {
    allow                 *
  }

  rewrite  {
    enable                0
    inherit               0

  }
  addDefaultCharset       off

  phpIniOverride  {

  }
}

rewrite  {
  enable                1
  autoLoadHtaccess        1
}
vhssl  {
            keyFile                 /etc/letsencrypt/live/subdomain.A.com/privkey.pem
            certFile                /etc/letsencrypt/live/subdomain.A.com/fullchain.pem
            certChain               1
        }
 
#6
The config looks right. If you visit HTTP://subdomain.A.com:8088/index.html directly, does it return 200 ok, or 404 not found?
:8088/index.html

when linking to

200,404, not

The following message appears
---------------------------------------------------------------

This site can’t be reached
subdomain.A.com:8088/index.html took too long to respond.
Try the following:
  • Check your connection
  • Check your proxy and firewall
  • ERR_CONNECTION_TIMED_OUT
--------------------------------------------------------------------




When I allowed firewall 8088 on the server reporting the above situation, the

subdomain.A.com:8088/index.html page is displayed fine

But the subdomain.A.com one is still a 404 error.
 
Last edited:
#8
Do you have port 8088 allowed on the server? :unsure:
I just thought of this myself and added a comment


When I allowed firewall 8088 on the server reporting the above situation, the

subdomain.A.com:8088/index.html page is displayed fine

But the subdomain.A.com one is still a 404 error.
 

Cold-Egg

Administrator
#9
Good.
If subdomain.A.com:8088/index.html loads fine, but subdomain.A.com:8088/, then it's auto index problem.
But you mentioned subdomain.A.com returns a 404, which is probably a domain mapping issue on the listener, have you map the domain on port 80/443?
 
#10
Good.
If subdomain.A.com:8088/index.html loads fine, but subdomain.A.com:8088/, then it's auto index problem.
But you mentioned subdomain.A.com returns a 404, which is probably a domain mapping issue on the listener, have you map the domain on port 80/443?
When entering that homepage into the 80/443 listener, the
subdomain.A.com:8088 will be connected.

However, because 80/443 is a WordPress attribute, it's not possible to use the
subdomain.A.com without 8088 is redirected to the main domain WordPress address with the message

https://A.com/wp-signup.php?new=subdomain


Message: Hello Network Administrator! Your network is not currently allowing registrations. To change or disable registration, go to the Options page.
Your registration has been disabled.
 
Top