Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 3 > Installation/Configuration

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 16th June 2012, 13:35
skarmoutsosv skarmoutsosv is offline
Junior Member
 
Join Date: Jun 2012
Location: Lagkadikia, Greece
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Thumbs down Error at "AliasDomain for website"

Error at "AliasDomain for website"

Hi all,
I followed the http://www.howtoforge.com/perfect-se...nx-ispconfig-3
Then I setup some dns, email and websites. All worked fine.

Then I needed to make domain2.org and domain3.org to have the same content with domain1.org, so I created two "Aliasdomain for website", both pointing to domain1.org
The above setting did not work as I expected. The domain2.org and domain3.org was serving a default ISPconfig web page.
I played around with "Aliasdomain for website" and "Subdomain for website" from ISPconfig control panel and finaly deleted all these entries. Without any entry, both domain2.org and domain3.org are showing the content of domain4.org !

I recreated the two "Aliasdomain for website" again but the result is as above.

How can I make domain2.org and domain3.org to stop pointing at domain4.org and start pointing at domain1.org?


P.S. I used only the control panel to do changes (I did not touch any file)
However, I see at /etc/nginx/sites-available a file called domain1.org.vhost.err

domain1.org is tsoumanis.eu
domain2.org is dikastikosgrafologos.gr
domain3.org is forensicdocumentexpert.gr
domain4.org is computerlab.gr

domain4 created without specific client (client0)
domain2 created for client1

Thank you in advance for you time to read this message.
Reply With Quote
Sponsored Links
  #2  
Old 17th June 2012, 18:52
skarmoutsosv skarmoutsosv is offline
Junior Member
 
Join Date: Jun 2012
Location: Lagkadikia, Greece
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
 
Smile Solved

I restarted nginx
Code:
/etc/init.d/nginx restart
and saw the message:

Quote:
Restarting nginx: nginx: [emerg] could not build the server_names_hash, you should increase server_names_hash_bucket_size: 32
nginx: configuration file /etc/nginx/nginx.conf test failed
Then I found at http://nginx.org/en/docs/http/server_names.html the following:

Quote:
If you have defined a large number of server names, or defined unusually long server names, you may need to tune the server_names_hash_max_size and server_names_hash_bucket_size directives at the http level. The default value of the server_names_hash_bucket_size may be equal to 32, or 64, or another value, depending on your CPU cache line size. If the default value is 32 and you define “too.long.server.name.example.org” as a server name, then nginx will fail to start and display the error message:

could not build the server_names_hash,
you should increase server_names_hash_bucket_size: 32

In this case, you should set the directive value to the next power of 2:

http {
server_names_hash_bucket_size 64;
...
So, i edited /etc/nginx/nginx.conf and uncomment the line:
Code:
server_names_hash_bucket_size 64;
Then I restarted nginx and my long name domains are working fine.

It could be nice to be informed from ISPconfig for the erroneous nginx setup.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 17:19.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.