[support] Gone live problem

Jamie Holly hovercrafter at earthlink.net
Mon Jun 18 18:22:52 UTC 2012


How exactly are you set up? Is drupal installed in ~/public_html or 
~/public_html/{some folder}. To access it, do you go to example.com or 
example.com/{some path - refers to some folder}


Jamie Holly
http://www.intoxination.net
http://www.hollyit.net


On 6/18/2012 2:13 PM, Anthony wrote:
> Yes I tried un-commenting and didn't help. Perplexing.
>
> On Mon, Jun 18, 2012 at 11:03 AM, Jamie Holly 
> <hovercrafter at earthlink.net <mailto:hovercrafter at earthlink.net>> wrote:
>
>     Generally you don't need it. Read the documentation in
>     settings.php to understand it.
>
>     Jamie Holly
>     http://www.intoxination.net
>     http://www.hollyit.net
>
>
>     On 6/18/2012 1:53 PM, Anthony wrote:
>>     So it should be used and set correctly?
>>
>>     On Mon, Jun 18, 2012 at 10:45 AM, Jamie Holly
>>     <hovercrafter at earthlink.net <mailto:hovercrafter at earthlink.net>>
>>     wrote:
>>
>>         Yup
>>
>>         Jamie Holly
>>         http://www.intoxination.net
>>         http://www.hollyit.net
>>
>>
>>         On 6/18/2012 1:27 PM, Anthony wrote:
>>>         # $base_url = 'http://66.147.244.79/~polamor1/polamnew
>>>         <http://66.147.244.79/%7Epolamor1/polamnew>';  // NO
>>>         trailing slash!
>>>
>>>         Does hash comment it out? polamnew is the old path.
>>>
>>>         On Mon, Jun 18, 2012 at 10:18 AM, Jamie Holly
>>>         <hovercrafter at earthlink.net
>>>         <mailto:hovercrafter at earthlink.net>> wrote:
>>>
>>>             You don't by chance have $base_url set in settings.php,
>>>             do you?
>>>
>>>             Jamie Holly
>>>             http://www.intoxination.net
>>>             http://www.hollyit.net
>>>
>>>
>>>             On 6/18/2012 1:07 PM, Anthony wrote:
>>>>             Wow. When I comment it out I get this:
>>>>             http://66.147.244.79/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/~polamor1/accounts
>>>>             <http://66.147.244.79/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/%7Epolamor1/accounts>
>>>>             when trying to go to the accounts page.
>>>>
>>>>             On Mon, Jun 18, 2012 at 9:34 AM, Jamie Holly
>>>>             <hovercrafter at earthlink.net
>>>>             <mailto:hovercrafter at earthlink.net>> wrote:
>>>>
>>>>                 Comment it out and it should fix it. I have a
>>>>                 client with Drupal installations in sub directories
>>>>                 as well as the root directory on BlueHost and none
>>>>                 of them need RewriteBase set.
>>>>
>>>>                 Jamie Holly
>>>>                 http://www.intoxination.net
>>>>                 http://www.hollyit.net
>>>>
>>>>
>>>>                 On 6/18/2012 12:25 PM, Anthony wrote:
>>>>>                 Thanks for all the info. As usual the devil is in
>>>>>                 the detail.  Let me try to explain exactly what I
>>>>>                 did.
>>>>>                 1. I didn't want to move our email from yahoo so I
>>>>>                 started asking Bluehost how to go about doing
>>>>>                 that. They said and I quote/"Changing your name
>>>>>                 servers to Bluehost would interrupt your mail
>>>>>                 unless you change your MX records with us to point
>>>>>                 to Yahoo before you change the nameservers.I went
>>>>>                 ahead and made the MX record change on our end,
>>>>>                 you can change the nameservers at anytime./"
>>>>>
>>>>>                 They also said (different dude 10 hours later).
>>>>>                 /"You can change the hosting of just the website
>>>>>                 to us by pointing just the a record of the domain
>>>>>                 to 66.147.244.79 <tel:66.147.244.79>.  This will
>>>>>                 change the domain but not the mx entries."/
>>>>>                 2. So I changed only the A-Record from yahoo to
>>>>>                 the ip address mentioned. Not the NS records on
>>>>>                 network solutions.
>>>>>                 3. Then got the error mentioned. Got to home page
>>>>>                 but no further. 500 errors.
>>>>>                 4. Looked in the .htaccess and saw the line
>>>>>                 RewriteBase /~polamor1/
>>>>>                 I suspect that this may be wrong and I have to
>>>>>                 comment this line out but due to my ignorance can
>>>>>                 not justify based on logic.
>>>>>
>>>>>                 Thanks
>>>>>                 Tony
>>>>>
>>>>>
>>>>>
>>>>>                 On Mon, Jun 18, 2012 at 8:06 AM, Jamie Holly
>>>>>                 <hovercrafter at earthlink.net
>>>>>                 <mailto:hovercrafter at earthlink.net>> wrote:
>>>>>
>>>>>                     First thing to do - make sure that your
>>>>>                     computer is going to the correct
>>>>>                     IP. From a command window:
>>>>>
>>>>>                     nslookup example.com <http://example.com>
>>>>>
>>>>>                     If the IP is right then check your server
>>>>>                     error logs. A 500 error is not
>>>>>                     a DNS error. It actually comes from a
>>>>>                     webserver (see RFC 2616). As long
>>>>>                     as you are going to the right server, then the
>>>>>                     big hint will lie within
>>>>>                     the server's error logs.
>>>>>
>>>>>                     Also make sure you have a CNAME set up:
>>>>>
>>>>>                     example.com <http://example.com>. A
>>>>>                     xxx.xxx.xxx.xxx
>>>>>                     www.example.com <http://www.example.com>.
>>>>>                     CNAME example.com <http://example.com>.
>>>>>
>>>>>                     You need to CNAME www. to your A record or it
>>>>>                     won't work since www. is
>>>>>                     viewed as a subdomain. This wouldn't lead to
>>>>>                     the error (you would just
>>>>>                     get a server not found error - no HTTP error
>>>>>                     codes), but it does prevent
>>>>>                     future problems of people who want to use the www.
>>>>>
>>>>>                     Jamie Holly
>>>>>                     http://www.intoxination.net
>>>>>                     http://www.hollyit.net
>>>>>
>>>>>
>>>>>                     On 6/18/2012 10:46 AM, Joel Willers wrote:
>>>>>                     > I was referring to his hosts file on his
>>>>>                     personal machine for testing. Editing your
>>>>>                     hosts file makes you not have to wait for DNS
>>>>>                     changes, as you're telling your browser what
>>>>>                     IP address it supposed to be used. I use it to
>>>>>                     see what happens if I want a site to go live
>>>>>                     but what to see the ramifications first.
>>>>>                     >
>>>>>                     > Joel
>>>>>                     >
>>>>>                     >
>>>>>                     > -----Original Message-----
>>>>>                     > From: support-bounces at drupal.org
>>>>>                     <mailto:support-bounces at drupal.org>
>>>>>                     [mailto:support-bounces at drupal.org
>>>>>                     <mailto:support-bounces at drupal.org>] On Behalf
>>>>>                     Of Earnie Boyd
>>>>>                     > Sent: Monday, June 18, 2012 9:40 AM
>>>>>                     > To: support at drupal.org
>>>>>                     <mailto:support at drupal.org>
>>>>>                     > Subject: Re: [support] Gone live problem
>>>>>                     >
>>>>>                     > On Mon, Jun 18, 2012 at 8:44 AM, Joel
>>>>>                     Willers wrote:
>>>>>                     > >  You can always change your 'hosts' file
>>>>>                     on your machine to test how something works
>>>>>                     without actually changing the A record. Just
>>>>>                     add a line with IP address and the URL you
>>>>>                     want it to take over. Just make sure you
>>>>>                     remove it, otherwise you might not notice
>>>>>                     problems in the future.
>>>>>                     >
>>>>>                     > I don't believe the OP has access to his
>>>>>                     /etc/hosts file and the provider will not do
>>>>>                     it for him.
>>>>>                     >
>>>>>                     > --
>>>>>                     > Earnie
>>>>>                     > -- https://sites.google.com/site/earnieboyd
>>>>>                     > --
>>>>>                     > [ Drupal support list |
>>>>>                     http://lists.drupal.org/ ]
>>>>>                     --
>>>>>                     [ Drupal support list | http://lists.drupal.org/ ]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>                 -- 
>>>>>
>>>>>                 */Anthony Stefan Maciejowski/*
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>                 --
>>>>                 [ Drupal support list | http://lists.drupal.org/ ]
>>>>
>>>>
>>>>
>>>>
>>>>             -- 
>>>>
>>>>             */Anthony Stefan Maciejowski/*
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>             --
>>>             [ Drupal support list | http://lists.drupal.org/ ]
>>>
>>>
>>>
>>>
>>>         -- 
>>>
>>>         */Anthony Stefan Maciejowski/*
>>>
>>>
>>>
>>>
>>>
>>
>>         --
>>         [ Drupal support list | http://lists.drupal.org/ ]
>>
>>
>>
>>
>>     -- 
>>
>>     */Anthony Stefan Maciejowski/*
>>
>>
>>
>>
>>
>
>     --
>     [ Drupal support list | http://lists.drupal.org/ ]
>
>
>
>
> -- 
>
> */Anthony Stefan Maciejowski/*
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20120618/827be7b7/attachment-0001.html 


More information about the support mailing list