If you are not sure which Today Tip article to open first, use this page as a diagnostic directory. The goal is to start with the failing layer instead of changing several unrelated settings at once.
Choose a guide by the symptom
| What you see | Begin here |
|---|---|
| Site down or a server error | HTTP error diagnostic guide |
| Editor cannot save | Admin and editor guide |
| Image upload or display failure | Images and media guide |
| Domain, certificate or redirect failure | Use the DNS, HTTPS or redirect hub below. |
| Tool or business workflow problem | Use the relevant topic section below. |
Start with the symptom, then identify the layer
- Record the exact error or symptom. Note the message, status code, affected URL, device, and approximate time.
- Check whether the problem is local or service-wide. Test another browser, device, or network when that is safe and relevant.
- Identify the responsible layer. Browser, DNS, CDN, hosting, PHP, WordPress, plugin, account, or marketplace issues require different fixes.
- Change one thing at a time. Confirm the result before moving to another layer.
WordPress and website diagnostics
For broad technical errors, begin with the most specific hub:
- WordPress HTTP Error Codes — 4xx and 5xx failures.
- Cloudflare Error Codes on WordPress — 1xxx, 52x, Workers, Snippets, DNS and edge-layer failures.
- WordPress Upload and File Errors — temporary folders, MIME types, write failures and storage problems.
- WordPress HTTPS and SSL Errors — certificate, mixed-content and TLS problems.
- WordPress Redirect Loops — site URLs, HTTPS, caching and login redirects.
- WordPress DNS Errors — NXDOMAIN, DNS_PROBE and missing records.
- WordPress Images and Media — featured images, broken files and Media Library problems.
- WordPress Admin and Editor Problems — REST API, Site Health and Block Editor failures.
- WordPress Content Not Showing — embeds, shortcodes, widgets, menus, comments, search and feeds.
Specific WordPress problems
- WordPress Admin Slow
- WordPress Database Connection Error
- WordPress ERR_CONNECTION_TIMED_OUT
- WordPress Headers Already Sent
- WordPress Sitemap Problems
- WordPress XML-RPC Blocked
Digital tools
These guides separate browser, network, storage and account causes before recommending reinstallations or broad resets:
E-commerce and selling
Use these guides when the issue is product visibility, pricing, conversion or marketplace operations rather than a WordPress error:
- How to Start Selling on Coupang
- Product Listing Not Getting Views
- Product Images Not Converting
- How to Price Products for Profit
- Common Marketplace Seller Mistakes
Online business
If the technical stack works but the business model, offer or conversion path is unclear, start here:
- Best Online Business Models for Beginners
- How to Choose a Profitable Niche
- How to Start an Online Business With a Small Budget
- Website Traffic but No Sales
How Today Tip organizes troubleshooting
Today Tip aims to separate the source of a problem before recommending changes. A browser error is not automatically a WordPress error. A Cloudflare response may occur before WordPress runs. A failed upload can come from storage, MIME restrictions, temporary folders or the network. An online-business conversion issue should not be treated like a hosting failure.
When a topic substantially overlaps another page, we consolidate the material into a broader diagnostic guide and redirect older overlapping URLs instead of keeping many near-identical pages live.
If you still cannot find the right guide, use the Contact page to suggest a correction or topic.