The page is not available

the hoster replied that everything is working, maybe the reason is something else?

do we look like fools?
let them ping their own server from the external network

The server ran out of space around Jan 2 22:30:11.

All problems because of this.

host response:
We do not conduct any work on the VPS without power from the side of the coristuvacha, including not cleanly at the place of the water initiative. At times, 39% of disk space is occupied on your server. After your call, we reloaded the server, but the site didn’t see the robot after that. Turn back, be a caress in support of Onebox.

Judging by the CRM logs, the problem appeared on September 3, 2022:
[2022-01-03 00:09:01]
point: /var/www/vilescrmoneboxc/web1/web/modules/voip/cron/cron-binotel.php
data: Array
(
[type] => 1
[message] => Uncaught ConnectionManager_Exception: Cannot connect to database: Connection refused in /var/www/vilesc
rmoneboxc/web1/web/packages/ConnectionManager/ConnectionManager_MySQLi.class.php:44
Stack trace:
#0 /var/www/vilescrmoneboxc/web1/web/packages/ConnectionManager/ConnectionManager_MySQLi... ConnectionManag
er_MySQLi->connect()
#1 /var/www/vilescrmoneboxc/web1/web/packages/SQLObject/SQLObject.class.php(917): ConnectionManager_MySQLi->escapeString
()
#2 /var/www/vilescrmoneboxc/web1/web/packages/SQLObject/SQLObject.class.php(946): SQLObject->makeWhereArray()
#3 /var/www/vilescrmoneboxc/web1/web/packages/SQLObject/SQLObject.class.php(1296): SQLObject->makeWhereString()
#4 /var/www/vilescrmoneboxc/web1/web/packages/SQLObject/SQLObject.class.php(1091): SQLObject->_makeQuery()
#5 /var/www/vilescrmoneboxc/web1/web/api/db/Xplatform.class.php(364): SQLObject->getNext()
#6 /var/www/vilescrmoneboxc/web1/web/api/services/SettingService.class.php(1183): Xplatform->getNext()
#7 /var/www/vilescrmoneboxc/web1/web/
[file] => /var/www/vilescrmoneboxc/web1/web/packages/ConnectionManager/ConnectionManager_MySQLi...
[line] => 44
)
Wanting to get data from the config in the console, it was a long way to get to the data base.
Return, be kind, to the retailers of the site.
Garny evening!

Here is the system log
Jan 2 22:25:01 viles systemd: Started Session 54934 of user root.
................................................. .................Jan 2 22:30:11 viles journal: Runtime journal is using 8.0M (max allowed 91.5M, trying to leave 137.2M free of 907
.0M available → current limit 91.5M).
Jan 2 22:30:11 viles kernel: Initializing cgroup subsys cpuset
Jan 2 22:30:11 viles kernel: Initializing cgroup subsys cpu
Jan 2 22:30:11 viles kernel: Initializing cgroup subsys cpuacct
Jan 2 22:30:11 viles kernel: Linux version 3.10.0-1127.10.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC) ) #1 SMP Wed Jun 3 1
04:28:03 UTC 2020
Jan 2 22:30:11 viles kernel: Command line: root=UUID=0635e2fb-4091-41e2-9a10-5efef849183a ro crashkernel=auto rhgb quiet LANG=en_US.UTF-8
Jan 2 22:30:11 viles kernel: ACPI in unprivileged domain disabled
Jan 2 22:30:11 viles kernel: e820: BIOS-provided physical RAM map:
Jan 2 22:30:11 viles kernel: Xen: [mem 0x0000000000000000-0x000000000009ffff] usable
Jan 2 22:30:11 viles kernel: Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Jan 2 22:30:11 viles kernel: Xen: [mem 0x0000000000100000-0x000000007fffffff] usable
Jan 2 22:30:11 viles kernel: NX (Execute Disable) protection: active
Jan 2 22:30:11 viles kernel: DMI not present or invalid.
Jan 2 22:30:11 viles kernel: e820: last_pfn=0x80000 max_arch_pfn=0x400000000
Jan 2 22:30:11 viles kernel: RAMDISK: [mem 0x02c00000-0x03c40fff]
Jan 2 22:30:11 viles kernel: NUMA turned off
Jan 2 22:30:11 viles kernel: Faking a node at [mem 0x0000000000000000-0x000000007fffffff]
Jan 2 22:30:11 viles kernel: NODE_DATA(0) allocated [mem 0x7fc06000-0x7fc2cfff]
Jan 2 22:30:11 viles kernel: Reserving 161MB of memory at 720MB for crashkernel (System RAM: 2047MB)
Jan 2 22:30:11 viles kernel: Zone ranges:
Jan 2 22:30:11 viles kernel: DMA [mem 0x00001000-0x00ffffff]
Jan 2 22:30:11 viles kernel: DMA32 [mem 0x01000000-0xffffffff]
Jan 2 22:30:11 viles kernel: Normal empty
Jan 2 22:30:11 viles kernel: Movable zone start for each node
Jan 2 22:30:11 viles kernel: Early memory node ranges
Jan 2 22:30:11 viles kernel: node 0: [mem 0x00001000-0x0009ffff]
Jan 2 22:30:11 viles kernel: node 0: [mem 0x00100000-0x7fffffff]
...
Jan 2 22:30:17 viles kdumpctl: kexec: failed to load kdump kernel
Jan 2 22:30:17 viles kdumpctl: Starting kdump: [FAILED]
Jan 2 22:30:17 viles systemd: Failed to start Crash recovery kernel arming.
Jan 2 22:30:17 viles systemd: Startup finished in 1.317s (kernel) + 725ms (initrd) + 5.494s (userspace) = 7.538s.
Jan 2 22:30:17 viles systemd: Unit kdump.service entered failed state.
Jan 2 22:30:17 viles systemd: kdump.service failed.
And so until today.
And yes, the hoster cleared the web server log.