based on user reports and queries over the last 24 hours
U1 HOST outage statistics
After updating DNS records, propagation takes up to 48 hours. If your site still doesn''t resolve after that window, check that the nameservers in your domain registrar match the ones listed in the U1 HOST control panel. A mismatch here is the most common culprit.
If you can''t get into your hosting account, first try resetting your password via the email link. If the email doesn''t arrive within a few minutes, check your spam folder. Persistent login errors often mean the session cookie is stale — clear browser cache and cookies, then retry.
- Make sure the domain points to the correct server IP before requesting the certificate
- Check that port 80 is open — Let''s Encrypt uses it for domain validation
- If the cert shows as issued but the browser still warns about an insecure connection, force HTTPS in your .htaccess or server config
- Re-issuing the certificate usually helps if the domain was recently migrated
A 500 error almost always means something in your code or configuration broke server-side. Pull the error log from the control panel — it''ll point to the exact file and line. Common causes are syntax errors, wrong file permissions (scripts need 644 or 755), and memory limit exceeded. You can raise the memory limit in php.ini or via .htaccess with ''php_value memory_limit 256M''.
Hosting plans have upload size and execution time limits. If large files won''t upload through your CMS, increase ''upload_max_filesize'' and ''post_max_size'' in php.ini. For timeouts, bump ''max_execution_time'' to 120 or higher. FTP upload is a reliable fallback when the web interface keeps dropping the connection.
- Verify SPF and DKIM records are set correctly in the DNS zone
- Check that your sending domain isn''t on a public blocklist
- Shared hosting IPs occasionally get flagged — contact support to request an IP reputation check
- Test outgoing mail with a tool like mail-tester before assuming a code issue
The ''Error establishing a database connection'' message means your CMS can''t reach MySQL. Open your config file (wp-config.php for WordPress) and confirm the DB host, name, user, and password match what''s shown in the U1 HOST panel under databases. If credentials are correct but the error persists, the database process may have crashed — restarting it from the panel or submitting a support ticket is the fastest fix.
U1 HOST
Your message will be published in about
5 minutes
Service administration will see your message