I’m Spanish and I use a translator to write messages to you, and the usernames got translated, which is why we had that problem. But I’ve fixed everything now so you can log in without any issues with incorrect translations.

You can access Hestia with:
URL: https://panel.apploveyou.com:8083/login/
Username: hestia
Password: TempHestia#2026!A1

There you have the complete environment with domains and databases.

I’ve checked the SSH access.

Please try again with the credentials I sent.

SSH Access:
Host: panel.apploveyou.com
Port: 22
Username: support
Password: Siberian#Temp2026!

Permissions: sudo enabled for troubleshooting

Server: Ubuntu 22.04 (Oracle Cloud)
Purpose: dedicated to Siberian CMS Platform Edition
A snapshot was created before granting access

I hope you can access it without further problems this time. I sincerely apologize for the inconvenience.

I know we can only communicate through the ticket system, but if there’s any way you can contact me more directly, I’m available whenever you need me.

Best regards, and thank you so much for your support. I sincerely apologize.
Susan

Root login is not working. Also, in the Hestia panel, there is any web domain configured nor any database. Did you remove everything?

Sincerely,
The Siberian Team
Fred

I have updated the server credentials. You can now access using administrator privileges:

Hestia Panel:
https://panel.apploveyou.com:8083
Username: soporte
Password: TempHestia#5291!

SSH / Root access:
Host: panel.apploveyou.com
Port: 22
Username: root
Password: TempRoot#8472Secure!

Please proceed with the installation and let me know once the work is completed so I can secure the server again.

Thank you.

Kind regards,
Susan

I’m sorry but none of these credentials are working. Please consider sending us root access, that’s the only way we can give you a 100% efficient support. We are used to do that, and we already worked like this with thousands of clients, you don’t have to worry.
Let me know.

Sincerely,
The Siberian Team
Fred

After much deliberation and sleepless nights, I don’t think it’s wise to hinder your help because I need to resolve this issue, and you are the only ones who can assist me.

Server access is ready:

Hestia Panel:
URL: https://panel.apploveyou.com:8083/login/
Username: support
Password: Siberian2026

SSH Access:
Host: panel.apploveyou.com
Port: 22
Username: support
Password: Siberian#Temp2026!

Permissions: sudo enabled for troubleshooting

Server: Ubuntu 22.04 (Oracle Cloud)
Purpose: dedicated to Siberian CMS Platform Edition
A snapshot was created before granting access

Please proceed with investigating the installation issue and the license validation error.

If possible, please let me know when you start and when you finish your work.

Best regards, and thank you so much for your support, Susan

First of all, thank you for your reply and for your support.

Before providing server access, I would like to briefly explain my situation. Over the past few weeks, I have been working on setting up the entire environment (server, panel, permissions, tests, etc.), and it has been a complex process that has required a significant amount of time and effort. Additionally, due to relying on a technician who did not handle the installation correctly, I have had to rebuild everything from scratch, dealing with multiple issues and inconsistencies along the way.

I have been working on this project since March 4th and, honestly, the accumulated stress is quite high. This is a very important project for me, both personally and professionally, and my goal is simply to get it working correctly so I can start building my web apps.

For this reason, server security is especially important to me at this stage. I understand that direct access would make your investigation easier, but I also need to maintain a reasonable level of control and trust regarding who accesses the system and under what conditions.

As a possible solution, I can provide temporary SSH access through a restricted user account (without sudo privileges), limited to the web environment and the installation directory. This would allow you to review the setup directly while maintaining overall server security.

Please let me know if this level of access would be sufficient for your investigation or if you require an alternative approach.

My intention is to fully collaborate in order to resolve this as quickly as possible, while still maintaining basic security safeguards.

Thank you for your understanding.

Kind regards,
Susan

Please send us a SSH root access as well as an admin access to your Hestia panel.

Sincerely,
The Siberian Team
Fred

Now, after following your instructions, a new problem has arisen during the installation: the license step returns a 404 error during setup.

I’m experiencing a problem during the installation of Siberian CMS (Platform Edition) and would like to provide a complete technical overview of my environment and the exact problem I’m currently encountering.

Server Environment
Server: Ubuntu 22.04 (Oracle Cloud)
Control Panel: HestiaCP
Web Stack: Nginx (reverse proxy) + Apache
PHP Version: 8.1
Domain: panel.apploveyou.com
DNS managed by Cloudflare (DNS-only mode, no proxy enabled)
⚙️ Current Server Status

We have fully verified and stabilized the server environment:

✔ Nginx and Apache are working correctly
✔ The domain resolves correctly (HTTP 200 OK)
✔ PHP is working without errors
✔ File permissions and ownership have been corrected
✔ A clean installation directory has been prepared
✔ There is no active SSL on the domain (clean HTTP environment)
✔ The .well-known directory is working correctly for HTTP validation (200 OK response)
Installation Process

We followed a procedure of Clean installation:

All previous installation attempts were completely removed.
The public_html directory was cleaned.
Only the official install.php file (17 KB installer provided after license purchase) was re-uploaded.
File permissions were corrected (hestia:www-data).
It was confirmed that the installer loads correctly in the browser.
The license activation step was completed.
❌ Problem encountered

When entering a valid license key during installation:

The installer attempts to redirect to a license validation step.

Instead of continuing with the installation, the following error appears:

Page not found (Error 404)

I’ve attached a test video so you can see the behavior: https://applicandosoluciones.hippovideo.io/s/QwR9nJzP

This occurs immediately after submitting the license.

Additional Technical Notes
The HTTP validation paths (.well-known/acme-challenge) are working correctly (200 OK).
There is currently no active SSL (clean HTTP environment confirmed).
There is no interference from the firewall or Cloudflare proxy (DNS-only mode).
Server logs show no internal Apache/Nginx errors at this step.
The problem occurs exclusively during the installer license validation process.

❗ Conclusion

Everything on the server is configured and working correctly.

The installation process fails only during license validation, returning a 404 error, which suggests:

The backend endpoint in the installer is missing or incorrect.

The Platform Edition installation package may be outdated or incomplete.

Or there may be a problem with license validation in the current version.

Request

Could you please confirm the following?:

Whether the installation package we are using is up to date.
If there have been any changes to the license validation endpoint.

Or if a full offline installation package is required instead of the web installer.

Thank you in advance for your help.

Best regards, Susan.

Actually there has been an issue during the installation resulting in a 500 error. First of all, we can see the domain is under https connection. That means you have a SSL installed for this domain prior the installation. Please remove the SSL certificate on this domain, then remove all the file and the database, create a new database and restart the installation (send the installation file again if you removed it in the previous step).

Sincerely,
The Siberian Team
Fred

I am trying to install Siberian CMS Platform Edition (PE) on a new server and I am facing an issue during the installation process that I have not been able to resolve, even after thoroughly reviewing the entire server environment.

Server context
System: Ubuntu 22.04 (Oracle Cloud VPS)
Control panel: HestiaCP
Web server: Nginx + Apache (standard Hestia reverse proxy setup)
PHP: 8.1 (CLI and FPM active)
Database: MariaDB managed by HestiaCP
Domain: panel.apploveyou.com
SSL: Let’s Encrypt (temporarily not relevant for the installation process)
⚠️ Initial situation

An initial installation attempt of Siberian CMS PE was performed and reached approximately 53% of the installation process, but it failed and remained incomplete.

After that:

The previous installation was completely removed
The entire web directory (public_html) was cleaned
The installation was restarted from scratch on a fully clean environment
Current environment checks

The server environment has been fully verified:

✔ Connectivity to Siberian servers
The server can successfully reach:
https://updates02.siberiancms.com/installs/get.php
Response: HTTP 200 OK
✔ PHP and extensions
PHP CLI 8.1 working correctly
cURL enabled in PHP
file_get_contents over HTTPS working properly
✔ Web server
Nginx + Apache running correctly
Installer accessible at:
http://panel.apploveyou.com/install.php
No 403/502 errors on initial access
❌ Current issue

The installer loads correctly, but fails when entering the license key.

Observed behavior:
Installation page loads without issues
License is entered correctly
After submission, the system returns:
404 errors on internal installer routes
Installation process cannot continue to the next step
Example errors:
/install.php/license returns 403 or 404 depending on the attempt
Installer cannot proceed past the license validation step
Additional tests performed
HTTPS connectivity verified → OK (200)
PHP cURL verified → OK
POST requests to installer → returns valid HTML response
Nginx and Apache configuration checked → working correctly
HestiaCP domain rebuild executed → no errors
Possible causes

Based on all tests performed, the issue appears to be related to one of the following:

The PE installer may be using outdated or deprecated endpoints
The license may still be in an incomplete state due to the previous installation attempt at 53%
The licensing server may be rejecting the current installation flow
The installer may not be fully compatible with the current Siberian backend endpoints
Request

I would kindly request:

Verification of the current license status
Reset of any previous incomplete installation linked to this domain
Confirmation whether the current PE installer version is valid and compatible with active endpoints
If necessary, access to an updated installer package

Thank you very much for your support.