Opened 5 years ago

Closed 5 years ago

#8326 closed Bug/Something is broken (worksforme)

new host with mediawiki redirecting to outside site

Reported by: HistoriCUSS Owned by: Dana
Priority: Low Component: Tech
Keywords: mediawiki lang-en chelsea Cc: historiCUSS
Sensitive: no


we are adding hosts for but won't change registrar dns record until they are prepped and working. -> (future home) -> (drupal installed) -> (media wiki installed)

first 2 are accessible, showing landing. the wiki is not working as it is being redirected outside to the WAN.

I created hosting order for with users wikiwikardo so home is on chelsea

I go to but it ignores local dns/server aliases and tries to connect to the existing live natgat2014 hosted elsewhere. ->

Perhaps it will work properly when we change the registrar's dns settings to point to MF ns. This is non-critical and can wait until we go live. But if some error is obvious, please advise. Maybe something the mediawiki install altered is the problem.

Change History (6)

comment:1 Changed 5 years ago by Dana

Owner: set to Dana
Status: newassigned

I believe you will need to add an A record to the DNS where was purchased for each of the sub-domains. So two A records will need to be created:

  • pointed to
  • pointed to

Do you know if that's been done?

comment:2 Changed 5 years ago by HistoriCUSS

That was never done for yet it works fine.

None of the DNS natgat2014.* domains have been updated at the registrar. There are no entries on the registrar's DNS for either dev.* or wiki.* These only exist on the Mayfirst server and DNS.

We are not ready to do live on the main domains so right now we are accessing via and dev.natgat* vis

something different seems to be happening with the future site for

Without mediawiki, just a fresh hosting order, I can reach the site as expected via and get the standard "This is the future home of the web site." message from index.html.

After I install mediawiki, it is redirecting to the future actual domain for some reason. The other 2 host sites with drupal don't do that.

Because it is redirecting somehow to the future hostname, it gives this error:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, cgiadmin@… and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

currently: = [] = []

comment:3 Changed 5 years ago by HistoriCUSS

I edited LocalSettings.php

## The protocol and server name to use in fully-qualified URLs $wgServer = "";

to be: "";

It now works. Looks like after the DNS cut over when the main site goes live this will have to be changed back.

I do not recall the install procedure, but I do not think there was any instructions on what domain/server URL to use. Advising to use the host until DNA is active might help.

comment:4 Changed 5 years ago by Dana

Hi Glen,

The is going to, which is a site on, so for each domain you will need to to update/add an A record for each sub-domain for it to point to the right hosting order and can be used for development or to access with the sub-domain. This would be done where the domain was purchased, not in the MF control panel, since the name servers aren't being used.



comment:5 Changed 5 years ago by HistoriCUSS

Cc: historiCUSS added

comment:6 Changed 5 years ago by HistoriCUSS

Resolution: worksforme
Status: assignedclosed is going to be under, in the future, when the site is ready for the public. We are developing it at but until that happens, the registrar's records point to other NS and other host servers, not yet. and wiki.natgat2014,net are only on the mayfirst name servers. they have not been created on the registrar's dns or their host parking server.

It will be 3 or 4 weeks before we cut over to make these sites public and the workaround I did by editing the wiki LocalSettings.php file at least makes it accessible now which it wasn't before.

so works for me - closing

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.