Two Techs at my web host tell me yes, and one is telling me that is not possible without a plugin like WordPress Multisite User Sync/Unsync. I could have sworn I did this 2 months ago natively (without plugins).

Thank you for your consideration

// Details link using API info, if available.
if ( isset( $plugin_data['slug'] ) && current_user_can( 'install_plugins' ) ) {

modified to activate_plugins.

Thanks!

Even though support.carvebot.com worked without a CNAME, it’s possible that your hosting provider (or GoDaddy) automatically created an A or CNAME record for it when it was added. You’ll want to double-check in your GoDaddy DNS zone that there is an A record or CNAME for forum.carvebot.com. If not:

• Try creating an A record for forum.carvebot.com pointing to your server’s IP address (same as your main domain).
• Wait for DNS propagation (can take up to a few hours).
• Then rerun AutoSSL in cPanel to issue the certificate.

Also, make sure that the subdomain is added as an alias or addon domain in cPanel under the correct root, though it sounds like you already did that.

You have CNAME’d support.carvebot.com to carvebot.com, which is why it works.

But there’s no such CNAME or A/AAAA record for forum.carvebot.com, so this subdomain does not resolve at all.

I’m not familiar with your provider’s DNS tools, but you’ll know you’re ready when you can get forum.carvebot.com to also return carvebot.com when you do a CNAME lookup here: https://dnschecker.org

This usually happens because WordPress (or the underlying server/email configuration) tries to distinguish emails from different subsites by prepending the site ID using plus addressing. However, many mail providers (like Hotmail, Outlook, and even some corporate servers) don’t accept these modified addresses. ✅ Here’s how we fixed it:

1. Override the default sender address using a filter – Add this to your theme’s functions.php file or a custom plugin:

phpCopy

Edit

add_filter('wp_mail_from', 'fix_wp_mail_from_address'); function fix_wp_mail_from_address($email) { return 'no-reply@yourdomain.com'; // Use a valid address on your domain } add_filter('wp_mail_from_name', 'fix_wp_mail_from_name'); function fix_wp_mail_from_name($name) { return 'Your Site Name'; // Customize this }

2. Use a proper SMTP plugin – We recommend WP Mail SMTP or Post SMTP. Set it up to send emails from a real, verified email address like no-reply@yourdomain.com. This avoids weird formatting and improves deliverability.

To read more about this, make sure to visit this website.

When I log in to the main site, the password is upgraded as expected. However, logging into a subsite with the same credentials fails with an “invalid password” error. Logging back into the main site still works…

Disabling Redis and clearing all user-related object cache groups did not resolve the issue in my case. The only reliable workaround was reverting to WordPress 6.7.2 and re-setting the user password using an old-style md5 hash — everything then works normally across all subsites.

This seems like a critical issue with how the new password hashing interacts with multisite and object caching. Hoping core addresses it soon.

Web site multisite:
I then went into the subsite multisite panel. Clicked Edit. Went into settings and set the siteurl and home from http to https.

That did it.
Hopefully others whom have forgot the process will come over this thread.