Connect access
SFTP for files, optional SSH for server diagnostics, or GitHub for agencies. We test the connection and never ask for root.
OpDesk
For WooCommerce, custom PHP/Laravel on your hosting, and GitHub repos for agencies — without needing a developer on call. Connect access, pay for diagnosis, and see what’s wrong before you approve any change.
One case. Clear steps. No engineer jargon required.
SFTP for files, optional SSH for server diagnostics, or GitHub for agencies. We test the connection and never ask for root.
A plain-language report: what’s wrong, how confident we are, and whether automated repair is in scope.
Accept the terms, pay for repair, and review which file changes we propose.
Backup first, apply to live, run quick checks, and auto-rollback if something fails.
Same flow: connect access → diagnose → approve → apply. Only the codebase type changes.
01
Broken checkout, plugin trouble, critical errors or a white screen after an update. Also cleanup of hacked sites — malware, blacklist warnings, and malicious redirects — when you own the site and grant access. Ideal for shop owners.
02
Sites with their own code on cPanel or a VPS. Bugs, pages that won’t load, broken forms and app logic — always with your approval before anything goes live.
03
Repos and apps on GitHub. After diagnosis and your approval, OpDesk opens a pull request with the fix — nothing merges until your team does.
Pick the method that fits the problem. Each protocol has a clear role — no open shell and no root.
01
The primary connection for diagnosis and repair. We read files and, only after your approval, update the web root — with a backup before every change.
02
Optional when the issue looks like hosting: logs, PHP version, disk space, permissions. We run only predefined diagnostic checks — not an open terminal and never root.
03
For agencies on git. We diagnose the repo, and on approve we open a pull request with the fix. You review and merge — nothing goes to main without you.
What SSH unlocks
SSH does not mean more automatic changes on the server. It means we spot faster when the issue is hosting — so you don’t chase a WooCommerce bug while the disk is full.
When the site goes down or uploads fail, we check whether the server is out of space — before digging aimlessly in code.
A white screen after an update is often a PHP mismatch. We surface it in diagnosis and tell you clearly if the hosting panel needs a change.
When plugins can’t write, cache won’t clear, or files are blocked by permissions — we separate that from a code bug.
Timeouts and slow pages can be RAM or server load. We flag it so you know whether you need a file repair or a hosting upgrade.
Clear scope, so you don’t pay for work we can’t solve automatically.
And other targeted technical issues — diagnosis tells you if an automatic fix is in scope.
Three fixed repair prices. No hourly surprises and no token bills.
Diagnosis
9 €
Cause, confidence, affected files, and a clear yes/no for repair.
DiagnosisRepair
48 € – 129 €
The repair price depends on difficulty (39 €, 70 €, or 120 €) and is shown before you pay. Includes backup, approval before live, and checks.
Pay for the repair only when we verify it worked.
If checks fail and we roll back, we automatically refund the repair fee. Diagnosis (9 €) stays separate — you see the repair price and why before you pay.
Diagnosis 9 €. Repair is 39 € (easy), 70 € (medium), or 120 € (hard), shown with the reasons before you pay. No Fix, No Charge applies to the repair fee.
What shop owners ask before sharing server access.
No. Every live change needs your explicit approval. Until then you only see diagnosis and proposed changes.
We take a file backup before deploy. If automated checks fail, we roll back and automatically refund the repair fee (No Fix, No Charge). You can also request rollback within 30 days.
No. You don’t need to know servers. Connection details come from your hosting panel (usually cPanel → FTP/SFTP accounts), or you can ask your host using the ready-made message we show on the connect form. Agencies can also use GitHub.
Diagnosis says clearly if we can proceed. If out of scope, you do not pay for repair. If you pay for repair and we cannot verify the fix, we refund the repair fee.
They’re encrypted, used only for the case, and removed from your dashboard when the job ends. Details on the Security page.
SFTP is for site files (diagnosis and approved repair). SSH is optional for server diagnostics — predefined checks like PHP version, disk space, and logs. We don’t open an unrestricted shell and we never ask for root.
Yes, when you own the site and grant access. Diagnosis looks for injected code, malicious redirects, suspicious files, and unknown admin users. Repair removes what we can change safely, only after you approve, with a backup and rollback. We also tell you to rotate passwords and salts, update plugins, and request a Safe Browsing review. We do not run attacks or a full penetration test. Google and other blacklist operators decide when a warning is lifted.
Scan the QR or pick your platform to install the app (PWA) on your home screen — no Play Store or App Store.