11
2
Budget: 2500 UAH Deadline: 1 day
Good day, I will restore the database functionality for you, access to the server from you
13
1
- Projects 14
- Rating -
- Rating 1 083
Budget: 5000 UAH Deadline: 1 day
Good day! I have quite some experience with similar problems. I can help you, for clarification of details, write in private.
Copy
1 July 2025
Proposals are currently absent
Freelancers are reviewing the task — proposals will appear here soon.
Proposals concealed
The list does not show proposals concealed by the client or freelancer with a Plus profile, as well as proposals violating rules
-
Mar'yan-Bogdan K. 30 June 2025Можете добавити логи помилок ?
-
Pavel V.
30 June 2025
З радістю, але не знаю де це дивитись.
Спробую дістати інформацію -
Pavel V.
30 June 2025
Можливо це воно
< 2025-06-30 09:17:42.360 MSK >ERROR: deadlock detected
< 2025-06-30 09:17:42.360 MSK >DETAIL: Process 18528 waits for ExclusiveLock on advisory lock [320617,0,12130896,1]; blocked by process 16740.
Process 16740 waits for ShareLock on advisory lock [320617,0,25666957,1]; blocked by process 18528.
Process 18528: SET STATEMENT_TIMEOUT TO 20000;
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_documentjournal5452'));
SET STATEMENT_TIMEOUT TO DEFAULT;
Process 16740: SET STATEMENT_TIMEOUT TO 20000;
SELECT pg_advisory_xact_lock_shared((SELECT oid::bigint FROM pg_class WHERE relname = '_document126'));
SELECT pg_advisory_xact_lock_shared((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2044'));
SELECT pg_advisory_xact_lock_shared((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2066'));
SELECT pg_advisory_xact_lock_shared((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2074'));
SELECT pg_advisory_xact_lock_shared((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2087'));
SELECT pg_advisory_xact_lock_shared((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt7217'));
SET STATEMENT_TIMEOUT TO DEFAULT;
< 2025-06-30 09:17:42.360 MSK >HINT: See server log for query details.
< 2025-06-30 09:17:42.360 MSK >STATEMENT: SET STATEMENT_TIMEOUT TO 20000;
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_documentjournal5452'));
SET STATEMENT_TIMEOUT TO DEFAULT;
< 2025-06-30 09:17:42.365 MSK >WARNING: there is no transaction in progress
< 2025-06-30 14:37:27.370 MSK >ERROR: canceling statement due to lock timeout
< 2025-06-30 14:37:27.370 MSK >STATEMENT: SET STATEMENT_TIMEOUT TO 20000;
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2044'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2066'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2074'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2087'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt7217'));
SET STATEMENT_TIMEOUT TO DEFAULT;
< 2025-06-30 14:37:27.374 MSK >WARNING: there is no transaction in progress
< 2025-06-30 14:37:33.434 MSK >ERROR: canceling statement due to lock timeout
< 2025-06-30 14:37:33.434 MSK >STATEMENT: SET STATEMENT_TIMEOUT TO 20000;
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_inforg5787'));
SET STATEMENT_TIMEOUT TO DEFAULT;
< 2025-06-30 14:37:33.436 MSK >WARNING: there is no transaction in progress
< 2025-06-30 14:37:41.246 MSK >ERROR: canceling statement due to lock timeout
< 2025-06-30 14:37:41.246 MSK >STATEMENT: SET STATEMENT_TIMEOUT TO 20000;
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_reference9180'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_reference9180_vt9227'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_reference9180_vt9236'));
SET STATEMENT_TIMEOUT TO DEFAULT;
< 2025-06-30 14:37:41.248 MSK >WARNING: there is no transaction in progress
< 2025-06-30 14:37:55.529 MSK >ERROR: canceling statement due to lock timeout
< 2025-06-30 14:37:55.529 MSK >STATEMENT: SET STATEMENT_TIMEOUT TO 20000;
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_inforg5787'));
SET STATEMENT_TIMEOUT TO DEFAULT;
< 2025-06-30 14:37:55.530 MSK >WARNING: there is no transaction in progress
< 2025-06-30 14:38:04.983 MSK >ERROR: canceling statement due to lock timeout
< 2025-06-30 14:38:04.983 MSK >STATEMENT: SET STATEMENT_TIMEOUT TO 20000;
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2044'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2066'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2074'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt2087'));
SELECT pg_advisory_xact_lock((SELECT oid::bigint FROM pg_class WHERE relname = '_document126_vt7217'));
SET STATEMENT_TIMEOUT TO DEFAULT;
< 2025-06-30 14:38:04.986 MSK >WARNING: there is no transaction in progress
< 2025-06-30 15:05:23.710 MSK >ERROR: canceling statement due to user request
< 2025-06-30 15:05:23.710 MSK >STATEMENT: SELECT
T1._IDRRef,
T1._Fld917
FROM _Reference72 T1
WHERE ((T1._ParentIDRRef IN
(SELECT
T2._REFFIELDRRef AS REFFIELDRRef
FROM pg_temp.tt23 T2)) OR (T1._IDRRef IN ('\\276''\\030\\251\\005\\271\\305\\237\\021\\347\\340\\346\\311\\216V\\001'::bytea, '\\254\\020\\030\\251\\005\\271\\305\\237\\021\\350\\011\\2612\\201\\203\\236'::bytea, '\\200\\330<\\354\\357#&\\211\\021\\357\\275b\\207 \\332\\314'::bytea, '\\264a\\030\\251\\005\\271\\305\\237\\021\\347\\237\\247l3\\306L'::bytea, '\\224w\\030\\251\\005\\271\\305\\237\\021\\3502i^2\\014\\012'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352''\\253\\210+\\251\\214'::bytea, '\\254\\036\\030\\251\\005\\271\\305\\237\\021\\350\\353o\\315\\202\\025\\022'::bytea, '\\224\\023\\030\\251\\005\\271\\305\\237\\021\\3526\\003\\241\\234\\034\\321'::bytea, '\\260\\017\\030\\251\\005\\271\\305\\237\\021\\351F0_l\\222\\374'::bytea, '\\243X\\0224Vx\\221#\\021\\347\\225\\376m\\007\\214}'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352#m\\266\\260\\241Y'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352(\\217\\243\\326\\375\\371'::bytea, '\\200\\344\\366\\350/\\362\\3648\\021\\352V\\334\\223\\325E\\321'::bytea, '\\201\\001\\366\\350/\\362\\3648\\021\\352\\356\\006sk\\025\\020'::bytea, '\\271\\342\\030\\251\\005\\271\\305\\237\\021\\350j\\\\\\242\\323EC'::bytea, '\\275\\267\\030\\251\\005\\271\\305\\237\\021\\3506L\\330Udr'::bytea, '\\254\\036\\030\\251\\005\\271\\305\\237\\021\\350\\353o\\315\\202\\025\\022'::bytea, '\\224w\\030\\251\\005\\271\\305\\237\\021\\3502\\304\\217\\2445*'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352''\\253\\210+\\251\\214'::bytea))) AND (T1._Marked = FALSE) AND (T1._Folder) = TRUE AND (T1._Fld917 <> ''::mvarchar)
< 2025-06-30 15:05:23.716 MSK >WARNING: there is no transaction in progress
< 2025-06-30 15:05:24.291 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:05:24.291 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:05:24.291 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:05:24.291 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:05:24.292 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:05:57.954 MSK >ERROR: canceling statement due to user request
< 2025-06-30 15:05:57.954 MSK >STATEMENT: SELECT
T1._IDRRef,
T1._Fld917
FROM _Reference72 T1
WHERE ((T1._ParentIDRRef IN
(SELECT
T2._REFFIELDRRef AS REFFIELDRRef
FROM pg_temp.tt2 T2)) OR (T1._IDRRef IN ('\\276''\\030\\251\\005\\271\\305\\237\\021\\347\\340\\346\\311\\216V\\001'::bytea, '\\254\\020\\030\\251\\005\\271\\305\\237\\021\\350\\011\\2612\\201\\203\\236'::bytea, '\\200\\330<\\354\\357#&\\211\\021\\357\\275b\\207 \\332\\314'::bytea, '\\264a\\030\\251\\005\\271\\305\\237\\021\\347\\237\\247l3\\306L'::bytea, '\\224w\\030\\251\\005\\271\\305\\237\\021\\3502i^2\\014\\012'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352''\\253\\210+\\251\\214'::bytea, '\\254\\036\\030\\251\\005\\271\\305\\237\\021\\350\\353o\\315\\202\\025\\022'::bytea, '\\224\\023\\030\\251\\005\\271\\305\\237\\021\\3526\\003\\241\\234\\034\\321'::bytea, '\\260\\017\\030\\251\\005\\271\\305\\237\\021\\351F0_l\\222\\374'::bytea, '\\243X\\0224Vx\\221#\\021\\347\\225\\376m\\007\\214}'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352#m\\266\\260\\241Y'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352(\\217\\243\\326\\375\\371'::bytea, '\\200\\344\\366\\350/\\362\\3648\\021\\352V\\334\\223\\325E\\321'::bytea, '\\201\\001\\366\\350/\\362\\3648\\021\\352\\356\\006sk\\025\\020'::bytea, '\\271\\342\\030\\251\\005\\271\\305\\237\\021\\350j\\\\\\242\\323EC'::bytea, '\\275\\267\\030\\251\\005\\271\\305\\237\\021\\3506L\\330Udr'::bytea, '\\254\\036\\030\\251\\005\\271\\305\\237\\021\\350\\353o\\315\\202\\025\\022'::bytea, '\\224w\\030\\251\\005\\271\\305\\237\\021\\3502\\304\\217\\2445*'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352''\\253\\210+\\251\\214'::bytea))) AND (T1._Marked = FALSE) AND (T1._Folder) = TRUE AND (T1._Fld917 <> ''::mvarchar)
< 2025-06-30 15:05:57.956 MSK >WARNING: there is no transaction in progress
< 2025-06-30 15:06:08.033 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:06:08.034 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:06:08.034 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:11:18.864 MSK >ERROR: canceling statement due to user request
< 2025-06-30 15:11:18.864 MSK >STATEMENT: SELECT
T1._IDRRef,
T1._Fld917
FROM _Reference72 T1
WHERE ((T1._ParentIDRRef IN
(SELECT
T2._REFFIELDRRef AS REFFIELDRRef
FROM pg_temp.tt13 T2)) OR (T1._IDRRef IN ('\\276''\\030\\251\\005\\271\\305\\237\\021\\347\\340\\346\\311\\216V\\001'::bytea, '\\254\\020\\030\\251\\005\\271\\305\\237\\021\\350\\011\\2612\\201\\203\\236'::bytea, '\\200\\330<\\354\\357#&\\211\\021\\357\\275b\\207 \\332\\314'::bytea, '\\264a\\030\\251\\005\\271\\305\\237\\021\\347\\237\\247l3\\306L'::bytea, '\\224w\\030\\251\\005\\271\\305\\237\\021\\3502i^2\\014\\012'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352''\\253\\210+\\251\\214'::bytea, '\\254\\036\\030\\251\\005\\271\\305\\237\\021\\350\\353o\\315\\202\\025\\022'::bytea, '\\224\\023\\030\\251\\005\\271\\305\\237\\021\\3526\\003\\241\\234\\034\\321'::bytea, '\\260\\017\\030\\251\\005\\271\\305\\237\\021\\351F0_l\\222\\374'::bytea, '\\243X\\0224Vx\\221#\\021\\347\\225\\376m\\007\\214}'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352#m\\266\\260\\241Y'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352(\\217\\243\\326\\375\\371'::bytea, '\\200\\344\\366\\350/\\362\\3648\\021\\352V\\334\\223\\325E\\321'::bytea, '\\201\\001\\366\\350/\\362\\3648\\021\\352\\356\\006sk\\025\\020'::bytea, '\\271\\342\\030\\251\\005\\271\\305\\237\\021\\350j\\\\\\242\\323EC'::bytea, '\\275\\267\\030\\251\\005\\271\\305\\237\\021\\3506L\\330Udr'::bytea, '\\254\\036\\030\\251\\005\\271\\305\\237\\021\\350\\353o\\315\\202\\025\\022'::bytea, '\\224w\\030\\251\\005\\271\\305\\237\\021\\3502\\304\\217\\2445*'::bytea, '\\237Q\\030\\251\\005\\271\\305\\237\\021\\352''\\253\\210+\\251\\214'::bytea))) AND (T1._Marked = FALSE) AND (T1._Folder) = TRUE AND (T1._Fld917 <> ''::mvarchar)
< 2025-06-30 15:11:18.868 MSK >WARNING: there is no transaction in progress
< 2025-06-30 15:11:19.230 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:11:19.232 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:11:19.232 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:11:19.232 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:11:19.232 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:11:19.233 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:11:19.233 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:11:19.233 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:11:19.234 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:11:19.234 MSK >LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
< 2025-06-30 15:27:35.227 MSK >LOG: received fast shutdown request
< 2025-06-30 15:27:35.239 MSK >LOG: aborting any active transactions
< 2025-06-30 15:27:35.259 MSK >LOG: worker process: logical replication launcher (PID 2360) exited with exit code 1
< 2025-06-30 15:27:35.279 MSK >LOG: shutting down
< 2025-06-30 15:27:35.448 MSK >LOG: database system is shut down
< 2025-06-30 15:27:43.938 MSK >LOG: database system was shut down at 2025-06-30 15:27:35 MSK
< 2025-06-30 15:27:43.980 MSK >LOG: database system is ready to accept connections
< 2025-06-30 15:40:17.549 MSK >LOG: received fast shutdown request
< 2025-06-30 15:40:17.553 MSK >LOG: aborting any active transactions
< 2025-06-30 15:40:17.568 MSK >LOG: worker process: logical replication launcher (PID 22080) exited with exit code 1
< 2025-06-30 15:40:17.586 MSK >LOG: shutting down
< 2025-06-30 15:40:17.655 MSK >LOG: database system is shut down
< 2025-06-30 15:40:19.062 MSK >LOG: database system was shut down at 2025-06-30 15:40:17 MSK
< 2025-06-30 15:40:19.095 MSK >LOG: database system is ready to accept connections
< 2025-06-30 15:43:43.316 MSK >LOG: database system was interrupted; last known up at 2025-06-30 15:40:19 MSK
< 2025-06-30 15:43:52.312 MSK >LOG: database system was not properly shut down; automatic recovery in progress
< 2025-06-30 15:43:52.320 MSK >LOG: redo starts at 269/8274E560
< 2025-06-30 15:43:52.320 MSK >LOG: invalid record length at 269/8274E598: wanted 24, got 0
< 2025-06-30 15:43:52.320 MSK >LOG: redo done at 269/8274E560
< 2025-06-30 15:43:52.368 MSK >LOG: database system is ready to accept connections
< 2025-06-30 15:53:51.840 MSK >FATAL: password authentication failed for user "postgres"
< 2025-06-30 15:53:51.840 MSK >DETAIL: Password does not match for user "postgres".
Connection matched pg_hba.conf line 83: "host all all ::1/128 md5"
< 2025-06-30 15:55:15.003 MSK >LOG: received fast shutdown request
< 2025-06-30 15:55:15.009 MSK >LOG: aborting any active transactions
< 2025-06-30 15:55:15.009 MSK >FATAL: terminating connection due to administrator command
< 2025-06-30 15:55:15.027 MSK >LOG: worker process: logical replication launcher (PID 2392) exited with exit code 1
< 2025-06-30 15:55:15.028 MSK >LOG: shutting down
< 2025-06-30 15:55:15.110 MSK >LOG: database system is shut down
< 2025-06-30 15:55:22.376 MSK >LOG: database system was shut down at 2025-06-30 15:55:15 MSK
< 2025-06-30 15:55:22.405 MSK >LOG: database system is ready to accept connections
< 2025-06-30 16:05:22.392 MSK >LOG: received SIGHUP, reloading configuration files
< 2025-06-30 16:05:51.683 MSK >LOG: received SIGHUP, reloading configuration files
< 2025-06-30 16:06:09.824 MSK >LOG: received fast shutdown request
< 2025-06-30 16:06:09.828 MSK >LOG: aborting any active transactions
< 2025-06-30 16:06:09.848 MSK >LOG: worker process: logical replication launcher (PID 3024) exited with exit code 1
< 2025-06-30 16:06:09.849 MSK >LOG: shutting down
< 2025-06-30 16:06:09.932 MSK >LOG: database system is shut down
< 2025-06-30 16:06:12.324 MSK >LOG: database system was shut down at 2025-06-30 16:06:09 MSK
< 2025-06-30 16:06:12.358 MSK >LOG: database system is ready to accept connections
< 2025-06-30 16:56:03.000 MSK >LOG: received fast shutdown request
< 2025-06-30 16:56:03.006 MSK >LOG: aborting any active transactions
< 2025-06-30 16:56:03.035 MSK >LOG: worker process: logical replication launcher (PID 5716) exited with exit code 1
< 2025-06-30 16:56:03.037 MSK >LOG: shutting down
< 2025-06-30 16:56:03.111 MSK >LOG: database system is shut down
< 2025-06-30 16:56:07.086 MSK >LOG: database system was shut down at 2025-06-30 16:56:03 MSK
< 2025-06-30 16:56:07.123 MSK >LOG: database system is ready to accept connections
< 2025-06-30 17:46:46.549 MSK >LOG: received SIGHUP, reloading configuration files
< 2025-06-30 17:47:12.352 MSK >LOG: received fast shutdown request
< 2025-06-30 17:47:12.359 MSK >LOG: aborting any active transactions
< 2025-06-30 17:47:12.389 MSK >LOG: worker process: logical replication launcher (PID 4048) exited with exit code 1
< 2025-06-30 17:47:12.390 MSK >LOG: shutting down
< 2025-06-30 17:47:12.466 MSK >LOG: database system is shut down
< 2025-06-30 17:47:18.354 MSK >LOG: database system was shut down at 2025-06-30 17:47:12 MSK
< 2025-06-30 17:47:18.388 MSK >LOG: database system is ready to accept connections
-
Dmitro U. 30 June 2025Завдання з розряду - "машина зламалася, треба відремонтувати".😁
І дівчина робить ставку з повідомленням: "Я знаю, як відремонтувати, звертайтеся!" 😂😂😂
Current freelance projects in the category System & Network Administration
Not specified
31 proposals
We are looking for an experienced system administrator to configure, optimize, and provide ongoing technical support for a corporate server. The main purpose of the server is to enable remote work for accountants in financial programs (1C) via RDP. Main responsibilities: Diagnosis and resolution of current issues: analyzing system logs (Event Viewer), identifying and eliminating the causes of unstable user connections to RDP. Optimization of RDP (RDS) performance: proper configuration of session policies, idle time limits, and connection parameters for stable operation of accountants. Ensuring server security: Closing/changing standard ports, protection against brute-force attacks and unauthorized access. Segregation of user rights (restricting administrator rights for work accounts). Configuration of the Firewall on the server. If necessary, deploying and configuring secure VPN access for client connections. Setting up backups: organizing automatic daily backups of 1C databases and system images with copies offloaded to an external independent storage. Administration: monitoring resources (CPU, RAM, disk subsystem), managing system snapshots. Candidate requirements: Deep knowledge of Windows Server and Remote Desktop Services (RDS / RDP). Experience with cloud infrastructure. Understanding the specifics of RDP operation under 1C (working with databases, criticality of micro-disruptions in connectivity). Experience in configuring security for Windows servers and protecting financial data. Skills in automating backups. Collaboration terms: We consider the option of payment for completing the initial pool of tasks (RDP setup + security + backups) with the possibility of transitioning to a monthly fixed payment for ongoing technical support and server monitoring. Please indicate your experience with similar tasks and the estimated cost of the initial audit and server setup in your response. P.S. BK "Tam De Dim" (https://tamdedim.com.ua/)
Not specified
37 proposals
We have a dedicated server on Hetzner with a website on Docker (+ Laravel framework) Contact with the developers has been lost Need to: - restore and change server access (probably SSH) - recommend a storage location and set up a full server backup with easy recovery, probably not on Hetzner for security - fix the logo that is not displaying for some reason (it's unclear why the file has become inaccessible) Important - there is no website backup, and there is no room for error. We will only consider experienced specialists.
Loading...
Loading...