based on user reports and queries over the last 24 hours
MIRhosting outage statistics
If the hosting dashboard freezes on login or throws a 504 error, start with a hard browser refresh (Ctrl+Shift+R). Clear cookies and cached data specifically for the MIRhosting domain — stale session tokens cause most of these freezes. Try a different browser before escalating to support.
Passive mode is the usual fix here. In your FTP client (FileZilla, WinSCP), switch to PASV mode and double-check that the port range 49152–65535 is not blocked by your local firewall. Also verify the FTP hostname matches exactly what''s listed in your hosting account — one wrong character breaks the handshake.
This almost always comes down to file permissions or a broken .htaccess. Set directories to 755 and files to 644 via the file manager. If you recently edited .htaccess, rename it temporarily to isolate the issue. Check the error log in the control panel — it''ll show the exact line causing the failure.
Three things to check in order:
- The database username and password in your config file match what''s set in the panel
- The database host is ''localhost'' or the specific internal address provided by MIRhosting, not an external IP
- The user actually has privileges assigned to that database — easy to miss after creating a new DB
After issuing or renewing an SSL cert, propagation takes up to 15 minutes. If the browser still shows ''not secure'' after that, check whether the domain''s DNS A-record points to the correct server IP. A mismatch between the cert domain and the actual hostname is the next most common cause.
If server notification emails or contact form messages go missing, the sending domain likely lacks proper SPF and DKIM records. Add the records that MIRhosting specifies in the DNS settings section of the panel. Also check that the destination inbox isn''t silently filtering messages into spam based on the server''s IP reputation.
High TTFB (time to first byte) usually points to PHP memory limits or too many concurrent processes. In the panel, raise the PHP memory_limit to at least 256M and enable OPcache if it''s available on your plan. If the slowness appeared after installing a plugin or module, disable it and retest — resource leaks from third-party code are a frequent culprit.
MIRhosting
Your message will be published in about
5 minutes
Service administration will see your message