Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.When drupal ids are enabled users cannot log in to their 'local' site as user@localname. The login attempt generates warning messages:
fsockopen(): unable to connect to localname :80 in /home/reviews/public_html/includes/common.inc on line 336.
fsockopen(): php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/reviews/public_html/includes/common.inc on line 336.
(Obviously localname refers to the name of the local site).
Users should be able to log in to the site that their username is created for by default if drupal ids are allowed (perhaps even if they aren't).
This is exacerbated by the default new user email, which lists the drupal id username and password beneath the 'local' username and password. Many users only read the bottom part and attempt to log in as user@sitename on their first login attempt. This fails and the user is immediately discouraged and gives up thinking the user id or password is broken.
Comments
Comment #1
greggles@drupal.org commentedThis seems like two bugs:
1. Inability to login to localsite when using the user@localsite notation - I was able to login to the drupal.org site using both greggles and greggles@drupal.org could not repeat this behavior so I believe this request is closed.
2. Request to change the text in the welcome email. Since this is user configurable, I believe this is a relatively low priority issue. Creating a patch for that should be trivial.
Comment #2
greggles@drupal.org commentedI don't believe that the default welcome email is as stated by this user. I just tested it and the email was:
username: asdf
password:
So I believe this whole issue no longer applies. Marking it as such.
Comment #3
(not verified) commented