Please log in. To create a new account, enter the name and password you want to use.
If you supplied an email address when you signed up or added a email later, you can have your password reset.
This user name doesn't exist. If you want to create a new account, just verify your password and log in.
This user name exists. If you want to create a new account, please choose a different name.
Enter the current email address you have registered in your profile. You'll get an email containing your new password.
You have no email address in your profile, so you can't have your password reset.
Password reset. Check your email in a few minutes
That account does not exist.
The email address specified is not registered with this account.
Delivery to this email address has failed.
During the past half-hour I've gotten a few 503 temporarily unavailable errors when loading pages. Reloading usually seems to work, but this is the first time I've ever seen that error here.
Did the connection limits unintentionally get reduced when when you eliminated the ayase sub-domain, or is something else going on?
Update: It does appears something was changed and only a single connection is allowed now? For years I had been using a maximum of 3 download connections + browsing (to stay under the previous limit) and it always worked fine.
Update2: Or not? The server actually seems to be randomly picking the number of connections to allow? At the moment the server is usually limiting me to only a single connection, but every once in awhile I can get 2 or 3 work. That combined with browsing pages producing 503, makes me think that maybe this wasn't an intentional change and the server is just overloaded/malfunctioning?
Update3: I was almost thinking this was a CloudFlare issue (which I'm now connecting through as of today), but after connecting to the site directly again, I'm still showing the same behavior with a firm 1 connection limit and occasional 503 errors when browsing. The 2 or 3 connections occasionally working I mentioned in Update 2 must be a side-effect of CloudFlare rarely having something cached. Whatever the case, these new connection limits seem overly restrictive
Cyberbeing
Did the connection limits unintentionally get reduced when when you eliminated the ayase sub-domain, or is something else going on?
Update: It does appears something was changed and only a single connection is allowed now? For years I had been using a maximum of 3 download connections + browsing (to stay under the previous limit) and it always worked fine.
Update2: Or not? The server actually seems to be randomly picking the number of connections to allow? At the moment the server is usually limiting me to only a single connection, but every once in awhile I can get 2 or 3 work. That combined with browsing pages producing 503, makes me think that maybe this wasn't an intentional change and the server is just overloaded/malfunctioning?
Update3: I was almost thinking this was a CloudFlare issue (which I'm now connecting through as of today), but after connecting to the site directly again, I'm still showing the same behavior with a firm 1 connection limit and occasional 503 errors when browsing. The 2 or 3 connections occasionally working I mentioned in Update 2 must be a side-effect of CloudFlare rarely having something cached. Whatever the case, these new connection limits seem overly restrictive