Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A 404 at /iredadmin is usually a web-server routing problem, not a missing iRedAdmin directory. Start with https://<your-server>/iredadmin/ (HTTPS and the trailing slash). If that still returns 404, verify that the request reaches the intended virtual host and that the iRedAdmin Nginx template or Apache WSGI mapping is active.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
The sequence below covers the common Nginx and legacy Apache layouts, custom URL changes, and the separate troubleshooting path for a 500 application error.
As an Amazon Associate I earn from qualifying purchases.
Start with the canonical iRedAdmin URL
Open the exact URL below, replacing the host name with the name configured for your mail server:
https://<your-server>/iredadmin/
- Use HTTPS, not HTTP.
- Keep the trailing slash after
iredadmin. - Use the host name that appears in the active web-server configuration, rather than an arbitrary IP address or an old alias.
iRedMail’s installation guidance specifies the HTTPS form. In a maintainer-supported case, changing from HTTP to HTTPS fixed the 404 after a reboot. The iRedMail developer ZhangHuangbin has also answered this symptom directly: “Please use httpS.”
#1 Best Overall
If the HTTPS URL works, the problem was the protocol or the way the server redirected the request. If it does not, continue without assuming that the iRedAdmin files are missing.
Use this repair order before changing files
- Record the installation and platform. Run
cat /etc/iredmail-releaseand note the iRedMail version, operating-system distribution, web server, mail back end (LDAP, MySQL or PostgreSQL), and the exact URL that returns 404. Paths and service names vary by release and operating system. - Confirm the request’s host name. Compare the host in your browser with the active
server_name(Nginx) or the matching SSL virtual host (Apache). A request sent to a different host can be handled by a default site that knows nothing about iRedAdmin. - Inspect the effective configuration. For Nginx, run
nginx -T, not just a single file read. This expands included files and shows which server block is actually loaded, whether the iRedAdmin template is included, and whether another default site can win the request. - Check the route itself. In the Nginx output, look for the
/iredadmin/locations and the include for/etc/nginx/templates/iredadmin.tmpl. On Apache, inspect the active SSL virtual host for the iRedAdmin WSGI and static aliases. - Validate before reloading. Run
nginx -tafter any Nginx edit. Only after it reports a successful test should you runsystemctl reload nginx(or the service command used by your distribution). Use the corresponding Apache syntax check and reload/restart command for an Apache deployment. - Watch the logs while reproducing the error. Request
https://<your-server>/iredadmin/while tailing the Nginx or Apache access and error logs. Capture the status code, host header and selected virtual host. This distinguishes a route that was never matched from an application that was reached and failed.
How to tell what a 404 means
A normal Nginx 404 for this symptom means the request did not match an iRedAdmin route in the server block that handled it. Typical causes are an excluded host name, an unloaded template, a competing default site, or a URL that was partially renamed. It does not, by itself, prove that the iRedAdmin directory or Python application has been deleted.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A 500 response is different: it means the request reached application code and that code failed. Do not install dependencies or replace application files merely because a 404 page mentions iRedAdmin. First confirm the status in the access log and the browser’s network response.
Nginx: repair the virtual host and template
1. Check that the browser host is in server_name
Open the complete configuration shown by nginx -T. Find the SSL server block that is supposed to serve mail administration and compare every name in its server_name directive with the name typed in the browser. Include the exact spelling and any required aliases.
A documented support case had an iRedAdmin template included in the default SSL file, but the administrator had changed server_name so it excluded localhost, the name used in the browser. Nginx consequently selected another server block and returned its generic 404. Restoring a matching host name, or browsing to a name that is actually configured, corrected the routing.
The access log helps verify this. Make one request and check whether it appears in the expected virtual host’s log. If it appears only in a default site’s log, fix host selection before touching the iRedAdmin application.
2. Confirm that iredadmin.tmpl is loaded
On the Linux and OpenBSD layouts covered by the iRedMail documentation, the usual template is:
Rank #2
- Standard size: 6 pink server note pads, Each Book Comes with 50 bound order slips - that's 300 ticket sheets total! Check Pads Size 6.75 x 3.5 inch.
- Convenient Work: These guest check books for servers have a tear-free dotted line that is easy to rip off. You can give as a customer copy or keep for record keeping. We've provided extra rows on the back for additional note taking.Perfect For Restaurants, Lounges, Hotels, Cafes, And Waiters To Use.
- Record Important Information: These server note pads can record important information.Each ticket has a unique serial number printed at the top, dates, order details, number of guests, order amount, table numbers etc. They are lightweight, small and can fit most aprons. They can be used on-demand and can help decrease errors in orders, while improving work efficiency.
- High Quality: Sturdy, Not Drop Powder, It's Thick, You Can Write On The Back And Front Easily.Their whole page printing has clear handwriting and a reasonable layout. On the customer retention part of each guest check, "THANK YOU" on the back to make customers feel appreciated.
- Contact Us: We're confident that the quality of the server note pads will go beyond your expectation. If you experience an issue, feel free to contact us, we'll appreciate it to learn from your experience, and we'll make it better
/etc/nginx/templates/iredadmin.tmpl
The template supplies the locations that forward /iredadmin/ to the application and serve its static files. ZhangHuangbin summarized the 404 diagnosis this way: “If it shows 404 page not found error, it means the template file /etc/nginx/templates/iredadmin.tmpl is not loaded.”
Use nginx -T to verify that the active SSL server includes this template. Checking that the file exists on disk is not enough; an include can be absent, commented out, placed in a different server block, or overridden by a later site. If you add or restore the include, preserve the surrounding configuration and keep a backup of the working file.
After the edit:
- Run
nginx -t. - Fix every syntax error reported by that command; do not reload a failed configuration.
- Run
systemctl reload nginx, or the equivalent reload command on your operating system. - Request the canonical HTTPS URL again and check the access log for the new status.
3. Look for a competing default site
Nginx chooses a server block based on the address, port, protocol and host header. A distribution’s default site can therefore answer the request before the block containing iRedAdmin appears relevant. The expanded output from nginx -T reveals duplicate or broad server_name entries and the default server for the SSL listen address.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not delete an unfamiliar site immediately. First identify which block handled the request, then make the host names unambiguous. If you disable a conflicting site, validate the resulting configuration and reload Nginx before testing again.
4. Treat a custom base URL as one change, not four
Some administrators replace /iredadmin with a private path. That can work, but every related directive must use the same new path. Update the following as a set:
- The Nginx
locationpattern. - The rewrite or redirect that normalizes the URL and trailing slash.
- The
uwsgi_param SCRIPT_NAMEvalue passed to the application. - The static-file
alias.
A partial edit can produce a 404 at the new path, redirect to the old path, or load the HTML while returning 404 for CSS and JavaScript. Compare all four values in the effective configuration, then run nginx -t and reload. Test both the base path and a static asset request so that a superficially working login page does not hide a broken alias.
5. Check changes made around certificates or host names
A recent certificate replacement, DNS change, hostname rename, or custom-site installation can alter which SSL server block is selected. Record those changes alongside the iRedMail release when investigating. A certificate can be valid while the request still reaches the wrong virtual host; TLS success is not proof that the iRedAdmin route is loaded.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteApache: inspect the active SSL virtual host
Apache is a legacy deployment path in iRedMail documentation, and its file locations differ by distribution and release. The important question is not whether a directive exists somewhere on disk, but whether it is enabled in the SSL virtual host that receives your request.
Required mappings
The documented mapping contains a WSGI route and a static-file alias equivalent to:
WSGIScriptAlias /iredadmin .../iredadmin.py/Alias /iredadmin/static .../static/
The ellipses above represent distribution-specific paths; copy the paths from the guide for your operating system and iRedMail release rather than guessing them. The slash after iredadmin.py is part of the documented mapping.
Check the site that is actually enabled
Inspect the active SSL virtual host and confirm that both mappings are inside it. A separate non-SSL virtual host, an old default site, or a duplicate name can answer the request first. In one support case, disabling a conflicting site, enabling the default SSL site, and reloading Apache made iRedAdmin functional.
Recommended Free Tools
Use your distribution’s Apache configuration test before reloading. Then reload or restart Apache with the platform’s service command, request https://<your-server>/iredadmin/, and review both access and error logs. If the log shows that another virtual host handled the request, correct the enabled-site or host-name selection rather than changing the WSGI script.
Choose the diagnostic path that matches your deployment
| Question | Nginx deployment | Legacy Apache deployment |
|---|---|---|
| Primary route to verify | Included /etc/nginx/templates/iredadmin.tmpl and its /iredadmin/ locations |
WSGIScriptAlias /iredadmin and the /iredadmin/static alias in the active SSL virtual host |
| First configuration view | nginx -T (effective, expanded configuration) |
Enabled SSL virtual-host configuration for the active site |
| Syntax check | nginx -t |
The Apache configuration-test command supplied by the distribution |
| Typical 404 cause | Host name excluded from server_name, template not included, competing default site, or incomplete custom path |
WSGI/static aliases absent from the selected SSL site or a conflicting enabled site wins |
| After a successful check | Reload Nginx with the system’s service command | Reload or restart Apache with the system’s service command |
| What varies by release | Template location, include structure and service name | Python, WSGI and iRedAdmin filesystem paths plus enabled-site layout |
Before choosing a repair, also confirm whether iRedAdmin was selected during the iRedMail installation. If it was not selected, the expected template or application files may not have been installed, and copying a route from an unrelated release can make the configuration less reliable. Use the release recorded by cat /etc/iredmail-release to select the matching installation documentation.
When the status is 500 instead of 404
A 500 requires application-level evidence. Inspect the iRedAdmin and web-server error logs for a Python traceback, and preserve the exact status and timestamp from the access log. One documented case reported:
Rank #4
- Used Book in Good Condition
ModuleNotFoundError: No module named 'web'
For that specific failure, the maintainer prescribed:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →pip3 install -U web.pyservice iredadmin restart
Those commands address the missing web.py dependency shown in that traceback; they are not a general cure for a 404. Installing packages into the wrong Python environment, or changing dependencies without a matching traceback, can create a second problem. Confirm the module error, the operating-system package layout and the service name before applying the fix.
Collect evidence a maintainer can use
When the route remains unavailable, gather a concise evidence bundle instead of repeatedly editing configuration:
- Output of
cat /etc/iredmail-release. - Operating-system distribution and release.
- Web server (Nginx or Apache) and its version if known.
- Mail back end: LDAP, MySQL or PostgreSQL.
- The exact URL, including whether it uses HTTP or HTTPS and whether the slash is present.
- The browser’s status code and response text.
- The relevant access-log line, including the host header and timestamp.
- The corresponding web-server and iRedAdmin error-log lines.
- Recent changes to Nginx or Apache sites, certificates, DNS, host names, Python packages or custom URL paths.
Redact passwords, private keys, session cookies and database credentials before sharing configuration or logs. Keep a dated backup of the active configuration so that a failed experiment can be reverted.
Common symptoms and the appropriate fix
The HTTP URL shows 404, but HTTPS works
Use the HTTPS URL as the canonical bookmark. If you need HTTP to redirect, configure that redirect in the web server after confirming the SSL virtual host; do not treat the HTTP 404 as evidence that the application is absent.
Only one host name returns 404
Compare that name with server_name or the Apache SSL virtual-host names. Add the intended alias to the correct site, or use the already-configured canonical name. Then validate and reload.
The route works after a reload but fails after reboot
Check that the include is in the persistent enabled configuration rather than a temporary generated file, and verify that the service starts with the same site set after boot. Re-run nginx -T after reboot to compare the effective configuration.
Best Value
- New
- Mint Condition
- Dispatch same day for order received before 12 noon
- Guaranteed packaging
- No quibbles returns
The login page loads but its styles or scripts are 404
This points to a static alias or custom-base-path mismatch. Confirm the static location and alias, the rewrite, and uwsgi_param SCRIPT_NAME all use the same base path. Test a real static-file request in the access log.
Both iRedAdmin and another mail web application show 404
Treat the shared symptom as evidence of virtual-host selection or an unloaded site configuration. Check the host header and selected server first; do not repair each application independently until you know the request is reaching the intended SSL virtual host.
Prevent the next outage
- Bookmark and document
https://<your-server>/iredadmin/, including the trailing slash. - Keep a copy of the last known-good Nginx or Apache configuration before editing.
- After every route, host-name or certificate change, run the web-server syntax check and perform a real HTTPS request.
- Record the iRedMail release and operating-system paths in your administration notes.
- Monitor access logs for unexpected 404s after reloads or reboots.
- Keep custom base-URL changes documented as a complete group of location, rewrite, script-name and static-alias edits.
The practical rule is simple: establish the HTTPS URL, prove which virtual host handled it, and then verify that the iRedAdmin route is included in that host. Only after a 200/redirect route is confirmed should you investigate application dependencies.
Frequently Asked Questions
Why does adding a trailing slash matter for iRedAdmin?
The documented endpoint is /iredadmin/. The slash lets the configured location and redirect rules match the canonical base path; test that exact form before diagnosing deeper failures.
Can a valid TLS certificate coexist with an iRedAdmin 404?
Yes. TLS only proves that a certificate was presented. The request can still be routed to the wrong SSL virtual host, whose default site returns 404.
Should I reinstall iRedAdmin when the page is not found?
Not as a first step. Verify the selected host, the Nginx template or Apache aliases, and the effective configuration. Reinstallation can obscure a routing error and overwrite useful evidence.
What information should I include when asking for help?
Provide the iRedMail release, operating system, web server, mail back end, exact HTTPS URL, status code, selected-host access-log line, error-log excerpt, and recent host-name, certificate or custom-site changes. Remove credentials and private keys.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
