nginx config: duplicate entries

[bjo]

Hi,

I moved a froxlor installation from one host to another. Now, for one subdomain some entries are created twice and I have no idea why:

	location /awstats {
		alias /var/customers/webs/foo/awstats/bar.de/;
		auth_basic "Restricted Area";
		auth_basic_user_file /etc/nginx/htpasswd/2-9dfa416d341032ff07e23a1c83f223db.htpasswd;
		alias /var/customers/webs/foo/awstats/bar.de/;
		auth_basic "Restricted Area";
		auth_basic_user_file /etc/nginx/htpasswd/2-9dfa416d341032ff07e23a1c83f223db.htpasswd;
	}
	location ~ ^/awstats-icon/(.*)$ {
		alias /usr/share/awstats/icon/$1;
		alias /usr/share/awstats/icon/$1;
	}
	location /anleitungen/ {
		auth_basic "Restricted Area";
		auth_basic_user_file /etc/nginx/htpasswd/2-32a3d9762b05ebe2d13c4cbe8e271039.htpasswd;
		auth_basic "Restricted Area";
		auth_basic_user_file /etc/nginx/htpasswd/2-32a3d9762b05ebe2d13c4cbe8e271039.htpasswd;

[bjo]

Sorry for the late reply, I'll explain how I moved the installation:

 

• moved /var/customers to the new server via rsync
• imported a dump of the froxlor-db
• removed the IP-adresses in the config and added the new ones

The customer-data was in /var/kunden before, so I changed /var/kunden to /var/customers in froxlor and also where I found it in the database.

 

Yep, it worked before, but the issue occurs every time I recreate the webserverconfig, so the nginx-config-cronjob is doing something wrong.

[d00p]

Did you also change the IP in the database? Check panel_ipsandports if there is the correct IP address

[bjo]

Yep, they are correct.

[d00p]

And you are using the latest stable Version 0.9.32?

[bjo]

The error still existed, but I found the reason now. The domain was listed twice in panel_domains (I have no idea why), they had both the same customerid, but appeared only once in the domainsettings.

[d00p]

I suppose they have not been put there twice on the old server then?

[bjo]

You're right, on the old server the entries were created once.

[d00p]

Can you tell us exactly how you transfered? Does not sound like a Froxlor bug as you stated it worked before