What settings are needed for giving the standard web-pages visibility to browser end-user?

My setup: No wordpress, just plain cyberpanel web-pages on my own site-domain

I made my web-files content visible (for the end-user viewing my site with browser) by putting this:

meta http-equiv=“content-type” content=“text/html; UTF-8”

…into web-files. (In this example the web-file name is: mypage) Also then the web-files do not need the html-suffix

So, with the above changes the following now works:


However, this still does not work:


(Yes, they are different: look closer.) :face_with_raised_eyebrow:

Any suggestions how to make a final fix?

Happy New Year @Wizard-of-FOSS

Which error did you get ?

The error is a web-page response with the following content:

Not Found
The resource requested could not be found on this server!

Proudly powered by LiteSpeed Web Server
Please be advised that LiteSpeed Technologies Inc. is not a web hosting company and, as such, has no control over content found on this site.

Jalo: Changing the: Rewrite Rules

Jalo: (Some info:

Jalo: (Excerpt from the above link) Rewrite Rules
This is one of the most notable and important changes regarding rewrite rules from Apache to OpenLiteSpeed. Earlier it was very difficult for end users to convert rewrite rules from Apache to OpenLiteSpeed even though the difference was very slight.

However, with slight configuration changes (end user need not do anything on their end), you can now directly copy your Apache rules to CyberPanel rewrite rules box, 407 without needed to change your rewrite rules.

That’s a big relief)

Jalo: Right, well since I am seeking a relief regarding: trailing slash not working.

Jalo: Doing a change; [ Changing the: Rewrite Rules ]

From this: cat: /home/mydomain.tld/public_html/.htaccess: No such file or directory

…to this:

<Directory "/home/mydomain.tld/public_html"> 
    <IfModule mod_rewrite.c> 
        RewriteEngine On 
        RewriteBase / 
        RewriteCond %{REQUEST_URI} /+[^\.]+$
        RewriteRule ^(.+[^/])$ %{REQUEST_URI}/ [R=301,L]

And: It now forces a trailing slash at the end of web page which then causes 404.

Any suggestions for correct approach?

Well, this did it:

Doing a change to; [ Changing the: Rewrite Rules ]

<Directory "/home/mydomain.tld/public_html"> 
    <IfModule mod_rewrite.c> 
        RewriteEngine On 
        RewriteBase / 
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteCond %{REQUEST_URI} /(.*)/$
        RewriteRule ^ /%1 [R=301,L]

Now all I still need is:

How to make the website work when actual htmlfileswith.html

That is htmlfiles have a html-suffix.

My current solution (see most above) is only temporary, because everything else (than cyberpanel) handles/edits/manages files with html-suffix.