MainWP is compatible with sites that use custom WordPress admin and login URLs. This is common when using security plugins that rename these paths to reduce brute force attacks.
What You’ll Learn
- Whether MainWP supports custom admin URLs
- Which changes are safe on child sites vs. Dashboard
- How MainWP handles custom paths automatically
Prerequisites
- MainWP Dashboard installed
- Understanding of which plugin modifies your login/admin URLs
Custom wp-admin Path
MainWP supports customized /wp-admin/ paths on child sites.
How It Works
When connecting to a child site, MainWP attempts to reach http://url.com/wp-admin/admin-ajax.php. If that fails, it automatically retries with http://url.com. This fallback mechanism allows MainWP to work with most custom wp-admin configurations.
Compatibility Summary
| Location | Custom wp-admin | Supported |
|---|
| Child sites | Changed path | Yes |
| Dashboard | Changed path | No - may cause issues |
Do not change the wp-admin path on your MainWP Dashboard site. This can cause various issues with Dashboard functionality. Only change wp-admin on child sites.
Custom wp-login.php URL
MainWP supports renamed wp-login.php URLs on both child sites and your Dashboard.
Compatibility Summary
| Location | Custom login URL | Supported |
|---|
| Child sites | Renamed login | Yes |
| Dashboard | Renamed login | Yes |
- WPS Hide Login
- Rename wp-login.php
- iThemes Security (now Solid Security)
- All-In-One Security
Common Issues
Jump to WP Admin Not Working
If Jump to WP Admin doesn’t work after changing login URLs:
- Clear your browser cache
- Verify the security plugin allows external logins
- Check that the URL in MainWP matches the actual site URL
- See Troubleshoot Jump to WP Admin
Connection Fails After Changing Paths
If your site stops connecting after changing admin paths:
- Ensure the MainWP Child plugin is still active
- Verify the site is accessible at its new path
- Resync the site from your Dashboard
- Check server error logs for blocked requests
Self-Check Checklist
