Support » Fixing WordPress » cannot login to non-SSL subdomain; forced redirects

Viewing 2 replies - 1 through 2 (of 2 total)
  • That shouldn’t be happening. It is probably a bad DNS settings of the TLD.

    1&1’s proprietary mindset strikes again.

    I decided to play around with their system today, and discovered that one must use their auto-installer on a subdomain.
    It adds custom .php files specifically to handle the subdomain and, though I didn’t call to verify, I’m sure it reconfigures httpd.conf as well.

    In case anyone’s wondering, primary and sub(s) are on the same 1&1 IP address, at least with their Basic shared plan.

    Once their system is happy with the auto install, one need only change wp-config for the new database (which the auto-installer creates and cannot be renamed), drop their default tables & import the desired stage ones, paste stage files either to their “clickandbuilds” folder or create the desired folder and voilĂ ! My theme options got nulled in the process, but a quick import fixed it.

    It would have been nice if 1&1 had mentioned somewhere that only the primary domain can have a manual WP installation. Nothing in their FAQs addresses this; they just mention the customer needs to be on the basic (non-managed) WP plan in order to have access to his/her own database.
    Google turned up nothing. I guess most customers immediately head for the auto-installer.. or end up calling tech support.

    • This reply was modified 2 years, 4 months ago by IT Hertz.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘cannot login to non-SSL subdomain; forced redirects’ is closed to new replies.