CB Admin

Yay!

Hi byron & djbob! Sorry for my slow follow-up, but thanks for the help. Yes, it's working now. I didn't think of that for the RewriteCond line -- I guess I was too focused on the RewriteRule's! :-P Nonetheless, I'm not sure why the rewrite rule lines given before -- which separately consider both names -- didn't work for our www. name. But now they do -- just tried. (Please see those below.) Did you do something else besides remove the caret, djbob? BTW... I guess you know that cPanel's management of rewrite rules in our main .htaccess file -- at least where Ruby and your proxy server are concerned -- really seems to suck. Even aside from the placement of rules that didn't work, it would add rules at the ending of other lines -- breaking the file! -- nor would it actually delete rules previously added when commanded to do so. My only resort was to hand-edit. Perhaps my experience is not the norm; but if not, I'd sure like to know why. Thanks again for your help, and TIA for any comments on the above. Following, for byron's sake ;-) and for reference to the above, are my rewrite lines, with commented-out lines I had tried earlier. (I replaced for this post the actual app/proxy port number with "NNNNN".) Cheers, -cba ====================================================== RewriteCond %{HTTP_HOST} chorusbreviarii.org$ RewriteRule .* "http\:\/\/127\.0\.0\.1\:NNNNN%{REQUEST_URI}" [P,L] ############################################################################# # # This is the style of rule spit out by cPanel. It works... barely. # Images and style elements are missing. (?) # # RewriteRule ^/?$ "http\:\/\/127\.0\.0\.1\:NNNNN%{REQUEST_URI}" [P,QSA,L] # # # Before, these would work for chorusbreviarii.org, but not for # www.chorusbreviarii.org ... Now they work for both. (?) # # RewriteCond %{HTTP_HOST} ^chorusbreviarii.org$ # RewriteRule .* "http\:\/\/127\.0\.0\.1\:NNNNN%{REQUEST_URI}" [P] # # RewriteCond %{HTTP_HOST} ^www.chorusbreviarii.org$ # RewriteRule .* "http\:\/\/127\.0\.0\.1\:NNNNN%{REQUEST_URI}" [P,L] # RewriteCond %{HTTP_HOST} ^chorusbreviarii.org$ [OR] # RewriteCond %{HTTP_HOST} ^www.chorusbreviarii.org$ # RewriteRule .* "http\:\/\/127\.0\.0\.1\:NNNNN%{REQUEST_URI}" [P,L] ======================================================

Hello! First: Username: chorbrev Domain: [www.]chorusbreviarii.org We've installed a Ruby app. The direct url w/port -- http://www.chorusbreviarii.org:12408/ -- works fine, with or without the "www." ... Also working fine, via a rewrite rule: http://chorusbreviarii.org/ However, nothing I've tried will get http://www.chorusbreviarii.org/ to work. Rewrite rules in any form will not match against the form with "www". Any ideas? Thanks much for any suggestions or help you can give me!

Thanks, djbob. IIRC from yesterday, the error page said something like -- only upper-/lower-case letters, numerals, and the good ol' underscore are allowed...

Hi, djbob! Not a big deal at all. I really didn't expect you do anything about the restriction itself, especially if that's how cPanel is delivered. I just hope that -- especially given that us would-be lusers can only try once per day to set up an account with you [*] -- you will consider giving us a fighting chance to get the password acceptable on the first try, by saying what the restriction is, up front... That could be put right there within the form next to the password input boxes, or handled by extending your existing Javascript input validation. My thanks for your time. -- [*] I have not yet been so lucky... When I tried this morning for the first time today, the system still thought I had exceeded my attempt quota. [username: chorbrev | Domain: chorusbreviarii.org]

Thanks very much, Wizard. Really, though, the heads-up on allowed chars in passwords at signup, isn't so much a "request" but rather a suggestion, for djbob or whomever, to consider adding to their to-do list. My most pressing need, however, is to actually get my account request submitted. I tried again this morning, but was given the "daily signup limit has been exceeded" error page. I thought I'd seen somewhere that that tracking is reset at midnight. Is that incorrect? Do you have a suggestion for this HH newbie for getting started? Thanks again!

First, my thanks to HelioHost for the free services - what a great offering to the Internet! I created an account here (on the Forums) first, as advised on the HelioHost Signup page. As is my habit, I entered a password containing at least one "special character", which seems to have worked just fine. So back on the Signup page, I do likewise, albeit with a different password. There is no advice there to indicate that, as I learned upon submittal, that there is a "letters+numbers+underscore only" policy on allowed password characters for a HelioHost account. Leaving aside my "Huh?" reaction, that there is no obvious advance warning of the policy, and that it is rather inconsistent with the character set allowed here on the Forums -- I am rather bumbed out that I must now wait another day to set up an account under my chosen account name. I gather that you've had a problem with bots, and that there have perhaps been some individuals overly taking advantage of your free service. However, I hope that you see that you should try to eliminate this gotcha in your signup procedures for us legitimate users. Thanks for reading. I've just taken a little time and read up more about your services... I had been referred here by a part-time developer acquaintance, and I had the impression going in that, in addition to the free account/service, there is a paid level of service, real paying customers, etc. Which I gather now is not the case... So, please accept my apologies. I'm sorry -- I didn't realize until now that HH is an all-volunteer effort. I hope you won't view my preceding post as a demanding-something-for-nothing gripe. I really appreciate what you are doing for the Internet -- thank you!