Hello,
It would be nice, if we had option of configuration sync between multiple servers.

Example: I have nginx on www1, I have nginx on www2. Both are running CentOS 6 and Ajenti-V. Right now, when I add new domain to www1, I have to also manually add domain to www2.

I would normally resolve it with rsync on /etc/nginx/, but I think I would break ajenti on a second server.

I am trying to configure a catch-all email account; however, after I configure it and try emailing it, I get

550 Unrouteable address

For the email address, I am using *@domain.com. Normal email addresses like example@domain.com work just fine. It is only the catch-all email address that is not working.

Any ideas?

Thanks.

После инсталиции php5-cgi он исчезает из модулей и apache не хочет работать в режиме модуля php как cgi

root@server:~# /usr/bin/php5-cgi -m
[PHP Modules]
bcmath
bz2
calendar
cgi-fcgi
Core
ctype
date
dba
dom
ereg
exif
fileinfo
filter
ftp
gd
gettext
hash
iconv
imagick
imap
json

The idea behind this is to redirect a user to the proper URL that you want them to use IE

server {
listen 192.168.11.1:80;
listen [ipv6 address]:80 ipv6only=off;
server_name www.example.com example.com *.example.net *.example.org *.oldexample.com;
return 301 $scheme://subdomain.example.com.com$request_uri;
}

We used one of these to redirect traffic from our old URLs to our new URLs but this is not an option in Ajenti, so we have to use an if statement in the advanced section, and if is evil.

Where i should put my config declarations for my website? I want to put this:

index index.php;
error_page 404 /Page/System/404/;
error_page 403 /403/;
autoindex off;
location / {
  if (-e $request_filename){
    rewrite ^/(.+).css$ /min/css.php?file=$request_filename break;
  }
  if (!-e $request_filename){
    rewrite ^/(.+) /xv.php/$1 break;
  }
}
location ~ ^(.*)\.(tpl|sql|tmp|config)$ {
  deny all;
}

But this didn't working on ajenti.

Можно как-нибудь сбросить настройки Ajenti на по умолчанию ??
У нас проблема в том что google chrome скачивает страницы в место отображения. 
через другие браузеры всё корректно отображается.

Hey,

Thank you for the good work you guys have made with Ajenti.

Everything is working fine, but I have a tiny problem.
Wordpress won't send any e-mail out. Logs tell me this:

Oct 16 11:56:17 li573-117 postfix/error[4725]: B7A96202EC: to=<you@example.com>, relay=none, delay=1632954, delays=1632893/61/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to example.com[93.184.216.119]:25: Connection timed out)
Oct 16 12:13:52 li573-117 postfix/pickup[4014]: 42D8B20428: uid=500 from=<www-data>
Oct 16 12:13:52 li573-117 postfix/cleanup[4864]: 42D8B20428: message-id=<d12ead9addb0e3b3a516718ab498bfae@mailheavy.com>
Oct 16 12:13:52 li573-117 postfix/qmgr[4015]: 42D8B20428: from=<www-data@li573-117.localdomain>, size=903, nrcpt=1 (queue active)
Oct 16 12:13:53 li573-117 postfix/smtp[4866]: 42D8B20428: to=<silver@ability.ee>, relay=ability.ee[195.222.15.87]:25, delay=0.77, delays=0.04/0.02/0.66/0.06, dsn=5.0.0, status=bounced (host ability.ee[195.222.15.87] said: 550-Verification failed for <www-data@li573-117.localdomain> 550-The mail server could not deliver mail to www-data@li573-117.localdomain. The account or domain may not exist, they may be blacklisted, or missing the proper dns entries. 550 Sender verify failed (in reply to RCPT TO command))
Oct 16 12:13:53 li573-117 postfix/cleanup[4864]: 10B2020460: message-id=<20141016121353.10B2020460@li573-117.localdomain>
Oct 16 12:13:53 li573-117 postfix/qmgr[4015]: 10B2020460: from=<>, size=3381, nrcpt=1 (queue active)
Oct 16 12:13:53 li573-117 postfix/bounce[4868]: 42D8B20428: sender non-delivery notification: 10B2020460
Oct 16 12:13:53 li573-117 postfix/qmgr[4015]: 42D8B20428: removed
Oct 16 12:13:53 li573-117 postfix/local[4869]: 10B2020460: to=<www-data@li573-117.localdomain>, relay=local, delay=0.01, delays=0/0.01/0/0, dsn=2.0.0, status=sent (delivered to mailbox)
Oct 16 12:13:53 li573-117 postfix/qmgr[4015]: 10B2020460: removed



Not sure what to do with that info though.

Any help would be greatly appreciated.

Best wishes,
Silver

When I try to install Ajenti from a server hosted on Amazon Web Services West (in Oregon), it times out because it is unable to reach the ajenti servers:

[root@ip-172-31-24-240 ~]# wget http://repo.ajenti.org/ajenti-repo-1.0-1.noarch.rp...
--2014-10-10 18:04:24-- http://repo.ajenti.org/ajenti-repo-1.0-1.noarch.rp...
Resolving repo.ajenti.org (repo.ajenti.org)... 198.232.124.224
Connecting to repo.ajenti.org (repo.ajenti.org)|198.232.124.224|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3327 (3.2K) [application/x-redhat-package-manager]
Saving to: âajenti-repo-1.0-1.noarch.rpmâ

0% [


But if I try to do it from a Amazon Web Servers East server in Virginia, it works:


[root@ip-172-31-39-128 whatever]# wget http://repo.ajenti.org/ajenti-repo-1.0-1.noarch.rp...
--2014-10-10 22:10:12-- http://repo.ajenti.org/ajenti-repo-1.0-1.noarch.rp...
Resolving repo.ajenti.org... 198.232.124.224
Connecting to repo.ajenti.org|198.232.124.224|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3327 (3.2K) [application/x-redhat-package-manager]
Saving to: `ajenti-repo-1.0-1.noarch.rpm.1'


100%[=================================================================>] 3,327 --.-K/s in 0s


2014-10-10 22:10:12 (201 MB/s) - `ajenti-repo-1.0-1.noarch.rpm.1' saved [3327/3327]


I have my AWS security groups *wide* open on both the AWS Oregon and Virginia server.

Is Ajenti blocking Amazon's Oregon availability zone IPs?

Thanks

Mike