Topic: server-manager access lost after domain change - solved

[JensK]

I have changed the domainname of my sme7 server because I have got a new domain name. The new domain name should be the new primary web of the server. I got into "configure this server" at the console and changed the name from "oldddomainname.dk" to "newdomainname.dk". Server name is the same (sme). Saved changes and all.

before the change server-manager worked ok. After the name change the server-manager doesn't work anymore. When I access https://sme.newdomainname.dk/server-manager i get 603 access forbidden.

I can access server-manager if I enter the local ip address like:
https://xx.xx.xx.xx/server-manager.
I am only trying to access server-manager from the internal network - same subnet as the SME

Everything else works ok like webmail, phpmyadmin etc.

Is there something I have overlooked in the process of changing the primary domain name of the server?

SME is running server only as it is behind a firewall allready. I have nat'ed needed ports through the firewall.
Regards
JK

[xboxer21]

if you had previously saved the SSL certificates in firefox, go to preferneces->advanced->security and delete the certificate and access the server-manager again.
hopefully this should do the trick. if not let us know.

Thanks

[bpivk]

Log into server manager pannel and check the "hostnames and adresses" configuration. You should see "Current list of hostnames for newdomainname.dk".

Then check if you have something like:
sme.newdomainname.dk    Self      192.168.0.1

[JensK]

Thanks for the very quick reply xboxer21.
I have just tried to delete all certificates regarding my sme server both those refering to the old domainname and the new domainname but it didn't help.

maybe I should mention that the server is an upgrade fra a sme 6.0.1-01. The upgrade was done by installing a new sme 7 server with new domainname and moving the sme 6 disk to the new server doing a CopyFromDisk migration of data.

The old server had the old domain name and the new server had the new domainname.

When i couldn't access server-manager after the upgrade I renamed the new server to the old domainname. When that didn't give me access to server-manager i renamed it back to the new domainname.

Even though the server and pc is on the same network (192.168.xx.xx) I have had to grant remote access to 192.168.xx.xx to gain access to server-manager thorugh:
https://192.168.xx.xx/server-manager.

Any good ideas how to solve this mess i have entered?
regards
JK

[JensK]

I have the right domainnames in hostnames and adresses. Both the new primary dimain name and my to other secondary domainnames.

All names ares listed as:
sme.newdomainname.dk self 192.168.xx.xx
mail.newdomainname.dk self 192.168.xx.xx
etc.

Then there is
sme.olddomainname.dk self 192.168.xx.xx
mail.olddomainname.dk self 192.168.xx.xx

Can it have influence that the server is setup with external DNS. I have an external DNS. I have enteret the sme 7 server in this dns. I have setup the sme to up use the external dns. All the domains is setup to resolve locally.
My DNS resolves the sme names to the right adress and the reply is not 404 not found but 603 forbidden so i believe that DNS is resolved ok.
JK

[JensK]

After looking through messages log with no lick i found this in the httpd log:

[notice] Graceful restart requested, doing restart
[Thu Nov 30 18:45:20 2006] [notice] Digest: generating secret for digest authentication ...
[Thu Nov 30 18:45:20 2006] [notice] Digest: done
[Thu Nov 30 18:45:20 2006] [warn] RSA server certificate CommonName (CN) `sme.newdomainname.dk' does NOT match server name!?
[Thu Nov 30 18:45:20 2006] [warn] RSA server certificate CommonName (CN) `sme.newdomainname.dk' does NOT match server name!?
[Thu Nov 30 18:45:20 2006] [warn] RSA server certificate CommonName (CN) `sme.newdomainname.dk' does NOT match server name!?
[Thu Nov 30 18:45:20 2006] [notice] Apache configured -- resuming normal operations
[Thu Nov 30 18:45:33 2006] [error] [client 212.242.xx.xx] client denied by server configuration: proxy:http://127.0.0.1:980/server-manager/

I think this is due to a routing problem in my setup of the DNS. I have tried to delete the entry for sme server in the dns and reenter with no luck. The problem is the line with the address  212.242.xx.xx. Aparently the server thinks that the pc comes from the outside wan and not from the lan eventhough they are on the same network.

If I make a nslookup the servername is resolved ok to 192.168.xx.xx on the pc from wich i try to access the server-manager.

[bpivk]

Can it have influence that the server is setup with external DNS.

This is not the problem. And it's strange that you have to set apropriate permission to access server manager.

[JensK]

I have found the error. It was my dns setup. I had entered the complete domainname up in the dns for the smeserver like "sme.newdomainname.dk" - doohhh my fault.

Apparently sme does a reverse lookup to check if the pc is in the same network/domain as the server.

My dns answered with "sme.newdomainname.dk.newdomainname.dk"
sme assumed therefor that the pc wasn't in the right domain/local network

I changed the manual dns entry for smeserver to "sme" only and not "sme.newdomainname.dk".

Everything now works as expected.
Lesson learned check and check references and setups again
JK