Coder Social home page Coder Social logo

vestacp's Introduction

VestaCP

The ultimate control panel with docker (thanks lagun4ik for a great start)

What's included?

  • ubuntu 16.04 lts + Vesta 0.9.8-25
  • nginx (proxy) -> apache2 -> php-fcgi - high performance and flexible implementation
  • ssh/sftp, letsencrypt, memcached, redis, MariaDB 10.2, postgresql 9.6, nodejs 12.x, golang 1.15.x, openvpn, mongodb, couchdb, .net core 3.1
  • folder redirection for data persistence and automatic daily backup provided by VestaCP
  • DNS, named, dovecot/roundcube, spamassassin, clamav, etc... -- disabled by default
  • vesta panel SSL (LE-issued) for mail and control panel - provide $HOSTNAME environment variable
  • added ability to also run php-fpm

Run this image:

mkdir -p /opt/vestacp/{vesta,home,backup}

docker run -d --restart=always \
-p 3322:22 -p 80:80 -p 443:443 -p 9088:8083 \
-v /opt/vestacp/vesta:/vesta -v /opt/vestacp/home:/home -v /opt/vestacp/backup:/backup \
niiknow/vestacp

Volumes

/vesta -- configurations

/home -- users data

/backup -- users backup

Authorization

Login: admin

To get the password, run

sudo docker exec $CONTAINER_ID cat /vesta-start/root/password.txt

Alternatively, you can change the password with:

sudo docker exec $CONTAINER_ID /usr/local/vesta/bin/v-change-user-password admin YOURNEWPASSWORD

SSH for FTP

FTP was not installed on purpose because it's not secure. Use SFTP instead on the 3322 port. Disable ssh if you don't really need it and use the Vesta FileManager plugin. Also, make sure you change the user shell in the Vesta panel in order to use ssh.

todo/done

  • redirected customizable config folders to /vesta, exclude /home. Home has been setup to be it's own volume. Do not try to redirect the home folder. It's like opening a big can of worms. There are all kind of breaking issues with having home as a symbolic link: Vesta FileManager breaking, Apache and Nginx breaking, SSL breaking, and so on...
  • Use incrond to watch /etc/{passwd,shadow,gshadow,group} and sync to /backup/.etc so remember to attach the backup volume if you want to save password across restart.
  • AWS CLI has been installed to simplify your backup lifestyle. You just need to setup a cron on VestaCP.
  • Update index.html to remove reference to VestaCP from default site for security.
  • Dovecot/roundcube email, and DNS services are disabled by default. Look at /home/admin/bin/my-startup.sh for instruction on how to re-enable these services. Remember to restart your container after updating my-startup.sh.
  • Replace phpmyadmin and phppgadmin with adminer.

misc/tested/verified

  • ssh/sftp, nginx, apache2, php7.3+ & v8js
  • log viewing in Vesta
  • backup and restore
  • Vesta FileManager
  • Letsencrypt
  • Sending/outgoing email, dovecot
  • adminer
  • Redis, Memcached
  • nodejs, golang
  • MariaDB/MySQL, PostgreSql, Mongodb
  • add incron to monitor and immediately backup /etc/{passwd,shadow,gshadow,group}
  • nginx pagespeed module
  • redirect awstats
  • multiple php{7.3,7.4,8.0} fcgi and fpm templates

your todo

  • I recommend the following:
  1. Since this is Docker, you can run as many services as you want but only expose request port.
  2. Change the default/initial admin password for security purpose.
  3. Instead of using the admin acccount, consider creating a different/separate credentials for different website/service. This will make it easier for backup and recovery; especially, when you need to move the user to a different installation.

extra

If you use this Docker for hosting and allow your user to login, I also recommend installing maldetect on the docker host to scan the /home volume.

Enjoy!!!

GeoIP Blocking

http {
    ...
    geoip2 /etc/nginx/geoip2/GeoLite2-Country.mmdb {
        auto_reload 5m;
        $geoip2_country_code default=US source=$remote_addr country iso_code;
    }
    ...
    map $geoip2_country_code $allowed_country {
        default yes;
        FK no;
        FM no;
        EH no;
    }
}

server {
    ...
    if ($allowed_country = no) {
        return 444;
    }
    ...
}

Release Notes

1.10.0 - add php8.0, remove php7.2, default php7.4. It is suggest that you start this like migrating server: backup and restore individual user.

1.9.3 - fix build and prep for php8.0

1.9.1 - build update for nginx 1.18.0, GoLang 1.14.3, nodejs 12, and phpv8js for php7.4

1.9.0 - remove php7.1 and add php7.4, update to GoLang 1.13.5 and dotnet 3.1

1.8.5 - build update for Vesta 0.9.8-25 and nginx 1.16.1

1.8.0 - replace phpmyadmin and phppgadmin with adminer.

1.6.0 - Add wordpress support. Fix MongoDB weird build issue. Python 3.7, DotNetCore 2.2, GoLang 1.12.5, and update postgis-2.4 to postgis-2.5

1.5.2 - with php7.3 support.

MIT

vestacp's People

Contributors

gpproton avatar hasithachamod avatar keyndark avatar lsgd avatar noogen avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

vestacp's Issues

PHP 7.2 support

Good job you guys are doing. Documentation says it supports PHP 7.2 but when I install on UBuntu, it install PHP 7.0 only.

ANy setting I can tweak to enable 7.2 ?

Wrong Command with Volumes

After running mkdir -p /opt/vestacp/{vesta,home,backup}, user made backup folder, but the next command it said:
docker run -d --restart=always -p 2222:22 -p 80:80 -p 443:443 -p 3306:3306 -p 5432:5432 -p 8083:8083 -v /opt/vestacp/vesta:/vesta -v /opt/vestacp/home:/home -v /opt/vestacp/data:/backup niiknow/vestacp

But user did not create /opt/vestacp/data before, so I think the /opt/vestacp/data:/backup should be /opt/vestacp/backup:/backup.

But even I change the command as /opt/vestacp/backup:/backup, Vesta still said there is not backup file but I am sure I put it right. Any idea about this?

Automatically backup to /backup

Hi,
I tried your awesome work and wondered if I need to active the incrond somehow?
Currently, the /backup folder does not contain anything.
How often are the data synced to /backup?

Bug in new panel ssl implementation

Recent deployment of new vestacp give me a chance to test out the new panel ssl implementation from Vesta. Error showing that it's not working. Undecided wether to rollback or implement fix to the script:

2/14/2018 9:26:25 AM*** Running /etc/my_init.d/startup.sh...
2/14/2018 9:26:25 AM[i] running for the 1st time
2/14/2018 9:26:25 AMfile has vanished: "/vesta-start/local/vesta/data/ips/172.17.0.3"
2/14/2018 9:26:39 AMrsync warning: some files vanished before they could be transferred (code 24) at main.c(1183) [sender=3.1.1]
2/14/2018 9:26:39 AM[i] init nginx
2/14/2018 9:26:39 AM[i] init fail2ban
2/14/2018 9:26:39 AM[i] running /home/admin/bin/my-startup.sh
2/14/2018 9:26:40 AM * Starting Apache httpd web server apache2
2/14/2018 9:26:40 AM/usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted)
2/14/2018 9:26:40 AMSetting ulimit failed. See README.Debian for more information.
2/14/2018 9:26:41 AM *
2/14/2018 9:26:41 AM * Starting MariaDB database server mysqld
2/14/2018 9:26:42 AM   ...done.
2/14/2018 9:26:42 AM * Starting PostgreSQL 9.5 database server
2/14/2018 9:26:44 AM   ...done.
2/14/2018 9:26:44 AM * Starting vesta-nginx vesta-nginx
2/14/2018 9:26:44 AM   ...done.
2/14/2018 9:26:44 AM * Starting vesta-php vesta-php
2/14/2018 9:26:44 AM   ...done.
2/14/2018 9:26:44 AM[i] running /bin/vesta-auto-ssl.sh
2/14/2018 9:26:49 AMError: web domain ***redacted*** doesn't exist
2/14/2018 9:26:49 AM*** Running /etc/rc.local...
2/14/2018 9:26:49 AM*** Booting runit daemon...
2/14/2018 9:26:49 AM*** Runit started as PID 417
2/14/2018 9:26:49 AMFeb 14 15:26:49 83b46051db4d syslog-ng[425]: syslog-ng starting up; version='3.5.6'

Not an issue, but question to maintainer

Hi, great work. I have question regarding VestaCP running in container. What is the purpose of this? You are actually maintaining Ubuntu which is in container, not a real host where container is running? So what's the purpose? Also, maybe I am wrong but the point is to have one process in container, not quite big number included there :) What do you think?

Panel not working

Hello i'm install vestacp using follow steps, but panel not working.

docker service - ok
image - ok

anyone can't help me? (im checked ports, all vesta ports closed, try open ports manual but not working).

Roundcube /webmail not accessible

Hi,
I'm starting Your's image of VestaCP, and the panel at 8083 works with no problems.

But when i want to access RoundCube webmail at /webmail I get 404.

Any ideas?

Error Establishing a Database Connection with WordPress

Sorry for using issue to ask help. As a greener I met some problems I can't handle.

I had build a VestaCP in docker and tried to transfer my backup into this Vesta instance.

But all my sites build with WordPress would warn me as "Error Establishing a Database Connection". I checked the localhost and account information. It doesn't seems like has any wrong.

I tried to use the /wp-admin/maint/repair.php option, unfortunately even this page would get Error Establishing a Database Connection too.

Due to docker do not include phpMyadmin, I can't not access the panel to check what is wrong.

Do you have any idea for this?

How do you overcome letsencrypt script problems?

Hello! Would you advise, how do you manage letsencrypt script to be working? I'm facing:
Error: LetsEncrypt account registration 400
sed: can't read /usr/local/vesta/data/queue/letsencrypt.pipe: No such file or directory

Installation Issue

I tried to install this on digitalocean 10$ droplet on Ubuntu 16.04 x64

sudo -s
sudo apt-get update && apt-get dist-upgrade && sudo apt-get upgrade
sudo apt-get install htop curl wget

apt install docker.io

root@vestacp:~# mkdir -p /opt/vestacp/{vesta,home,backup}
// I've to set the folder permissions to 777 to make it work

root@vestacp:# docker run -d --restart=always
-p 3322:22 -p 80:80 -p 443:443 -p 9088:8083
-v /opt/vestacp/vesta:/vesta -v /opt/vestacp/home:/home -v /opt/vestacp/backup:/backup
niiknow/vestacp
Unable to find image 'niiknow/vestacp:latest' locally
latest: Pulling from niiknow/vestacp
5aaf623c6854: Pull complete
bba296685e48: Pull complete
cce127dfec89: Pull complete
d29fb82dcb8f: Pull complete
76667ab62645: Pull complete
edac414a540d: Pull complete
68dccdc76516: Pull complete
Digest: sha256:69ccafe98c301872b74a6fd996fa62e4e1dab8181bd05ddb42864d6f5d68b087
Status: Downloaded newer image for niiknow/vestacp:latest
263f9ee5f429d196072133e5c5523b3c2b04302d5b2e353cd20a454ddb7f4c9f
root@vestacp:
#

but when i try to access the Vestacp at 8083 "This site can’t be reached"

only port 80 works fine

image

any suggestions? I'm using the docker for the first time tbh lol

MYSQL Error: Connection to localhost failed

When I trying create new MySql DB I getting error Error: Connection to localhost failed
Also in ....:8083/list/db/ I see only phppgadmin link, but direct link to phpmyadmin http://...../phpmyadmin/ available.

My sh my-startup.sh

#!/bin/sh

# re-enable phpmyadmin and phppgadmin
rsync -a /etc/apache2/conf-d/php*.conf /etc/apache2/conf.d

# required startup and of course vesta
cd /etc/init.d/
./disable-transparent-hugepages defaults

# the 5 services below are enabled to support mininum default backup job
./apache2 start
./mysql start

# delete defult postgres admindb if not use, then comment out the line below
# ./postgresql start
./nginx start
./vesta start

# && ./exim4 start \
# && ./dovecot start \
# && ./clamav-daemon start \
# && ./spamassassin start \
# && ./php7.1-fpm start \
# && ./fail2ban start \ # -- only if you run with: --cap-add=NET_ADMIN --cap-add=NET_RAW

1.8.2: Container can't run init scripts and fails

When I run the Docker image with tag 1.8.2:

docker run -d --restart=always -p 3322:22 -p 80:80 -p 443:443 -p 9088:8083 -v /volumes/vestacp/vesta:/vesta -v /volumes/vestacp/home:/home -v /volumes/vestacp/backup:/backup niiknow/vestacp:1.8.2

Container fails to run scripts inside.

The container's log:

*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
No SSH host key available. Generating one...
/var/lib/dpkg/info/openssh-server.postinst: 164: /var/lib/dpkg/info/openssh-server.postinst: cannot create /etc/ssh/sshd_config: Directory nonexistent
*** /etc/my_init.d/00_regen_ssh_host_keys.sh failed with status 2

In the /volumes/vestacp directory I have three empty folders: vesta,home,backup

Error When Running Nginx

Today I found my website can't access anymore, and found that Nginx didn't start up.
When I try to start it in console, it said:

 sudo nginx -s reload
nginx: [emerg] open() "/etc/nginx/conf.d/dbadmin.inc" failed (2: No such file or directory) in /home/admin/web/{DomainHere}/private/dbadmin.conf:1

Since it said lacks of some file, I tried to follow the way mentioned in #88 :

sudo rsync -avh /vesta-start/etc/nginx/conf.d/*.inc /etc/etc/nginx/conf.d/
sudo nginx -t
sudo nginx -s reload

And get success to sync the files:

sudo rsync -avh /vesta-start/etc/nginx/conf.d/*.inc /etc/etc/nginx/conf.d/
sending incremental file list

sent 96 bytes  received 12 bytes  216.00 bytes/sec
total size is 1.05K  speedup is 9.70
ls /etc/etc/nginx/conf.d
dbadmin.inc  phpmyadmin.inc  phppgadmin.inc  webmail.inc

But when I went to niginx -t again, it still said:

sudo nginx -t
nginx: [emerg] open() "/etc/nginx/conf.d/dbadmin.inc" failed (2: No such file or directory) in /home/admin/web/{DomainHere}/private/dbadmin.conf:1

What should I do next?

phpMyAdmin: Connection for controluser as defined in your configuration failed.

While logging into phpMyAdmin with the credentials of the auto generated db table, I'm getting the following error on the Import tab.

Warning in ./libraries/plugin_interface.lib.php#532
 count(): Parameter must be an array or an object that implements Countable

Backtrace

./libraries/display_import.lib.php#368: PMA_pluginGetOptions(
string 'Import',
array,
)
./libraries/display_import.lib.php#453: PMA_getHtmlForImportOptionsFormat(array)
./libraries/display_import.lib.php#684: PMA_getHtmlForImport(
string '5ce295a3eb257',
string 'database',
string 'admin_default',
string '',
integer 629145600,
array,
NULL,
NULL,
string '',
)
./db_import.php#40: PMA_getImportDisplay(
string 'database',
string 'admin_default',
string '',
integer 629145600,
)

HTTPS

By default I can't to open my web site through HTTPS.
Also I don't see no one https config in /home/admin/web/...
What I have to do?

Postgresql shared buffer allocation

Heya, just FYI for anyone else who's trying to run this docker image on small VPS with less than 4Gb RAM, Postgresql shared buffer is set to 2GB which will make Postgresql to fail upon startup.

You can fix this by tweaking postgresql config file.

As an idea, could it be possible to pass this setting as env variable to the docker container?

Problems with configuration

I found this awesome project today. I'm trying to deploy it but maybe it's a lack of configuration.

How can I add the IP's into the system? I have several IP's bind to the host machine but I don't know how to map them inside. What's the process to replace your demo domain to a real domain?

Some help on README will be appreciated :)

ECS & EFS

Hello guys,

Thank you for your amazing work, I am learning docker and trying to figure out how to scale your container on an ECS environment using EFS to persist data.
Anyone willing to collaborate on this ?

Cheers,
Franck

Graph not generated

Hi

I am using your image to deploy my vesta server. Other working great but not showing the image on the Graph section.

Thanks

Setup nginx + php-fpm instead apache

Hi,

Can you add configuration for setup nginx + php-fpm instead apache and exclude apache, please.
Or how I can configure it for myself, and care about next updates?

Not able to get VestaCP working

So I'm having issues getting the VestaCP docker working. I install it through portainer and make all the ports public so I can try to access VestaCP from my client, however, none of the ports work except for one. The one that works also only gives 4571c112d7a1.example.com "Powered by Nginx".

phpmyadmin doesn't work

phpmyadmin doesn't work.
also when I trying to add new mysql db got an error: Error: Connection to localhost failed

when I execute command 'Error: mysqld restart failed' receiving this error

v-restart-service mysqld
Error: mysqld restart failed

My conf:

#!/bin/sh

# re-enable phpmyadmin and phppgadmin
rsync -a /etc/apache2/conf-d/php*.conf /etc/apache2/conf.d

# required startup and of course vesta
cd /etc/init.d/
./disable-transparent-hugepages defaults

# the 5 services below are enabled to support mininum default backup job
./apache2 start
./mysql start

# delete defult postgres admindb if not use, then comment out the line below
#./postgresql start
./nginx start
./vesta start

# && ./exim4 start \
# && ./dovecot start \
# && ./clamav-daemon start \
# && ./spamassassin start \
# && ./php7.1-fpm start \
# && ./fail2ban start \ # -- only if you run with: --cap-add=NET_ADMIN --cap-add=NET_RAW

PHPMYADMIN Unaccessible

Now by default, click PHPMYADMIN in the database tabs in VestaCP would take user to domain.com/phpmyadmin, but it weill return 404 error.
I wonder if it is not accessible by default? If it is, how to enable it?

Unable to start /usr/local/vesta/nginx/sbin/vesta-nginx (Permission denied)

Hi, i'm trying to start the vestacp service... the container (build from docker-compose) when start report this error:

start-stop-daemon: unable to start /usr/local/vesta/nginx/sbin/vesta-nginx (Permission denied)
i have tried also to run via command line
root@9e4c06c027e8:/# /etc/init.d/vesta start

  • Starting vesta-nginx vesta-nginx start-stop-daemon: unable to start /usr/local/vesta/nginx/sbin/vesta-nginx (Permission denied)

the permission on file is :
-rwxr-xr-x 1 root root 5806096 Jun 28 06:42 vesta-nginx
root@9e4c06c027e8:/usr/local/vesta/nginx/sbin#

Make VestaCP Run https://vps_ip_address:8083

Ubuntu 16.0.x

First, I run this series of commands to set up the Docker repository.

$ sudo apt-get install apt-transport-https ca-certificates curl
$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
$ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
$ sudo apt-get update

Once the repository has been installed, I can install the latest version of Docker CE.

$ sudo apt-get install docker-ce

Automatic start docker

$ sudo systemctl enable docker

Installing docker-compose

$ sudo -i
$ curl -L https://github.com/docker/compose/releases/download/1.17.1/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
$ chmod +x /usr/local/bin/docker-compose

After installing the docker I tried to run niiknow/vesacp

mkdir -p /opt/vestacp/{vesta,home,backup}

docker run -d --restart=always \
-p 2222:22 -p 80:80 -p 443:443 -p 3306:3306 -p 5432:5432 -p 8083:8083 \
-v /opt/vestacp/vesta:/vesta -v /opt/vestacp/home:/home -v /opt/vestacp/backup:/backup \
niiknow/vestacp

service docker status

docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-05-09 02:22:44 UTC; 9min ago
     Docs: https://docs.docker.com
 Main PID: 12595 (dockerd)
   CGroup: /system.slice/docker.service
           ├─12595 /usr/bin/dockerd -H fd://
           ├─12601 docker-containerd --config /var/run/docker/containerd/containerd.toml
           ├─13877 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8083 -container-ip 172.17.0.2 -container-port 8083
           ├─13898 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 5432 -container-ip 172.17.0.2 -container-port 5432
           ├─13910 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 3306 -container-ip 172.17.0.2 -container-port 3306
           ├─13921 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 443 -container-ip 172.17.0.2 -container-port 443
           ├─13932 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 2222 -container-ip 172.17.0.2 -container-port 22
           ├─13943 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 80 -container-ip 172.17.0.2 -container-port 80
           └─13948 docker-containerd-shim -namespace moby -workdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/b3cb5382bc33af67787cd67bef26e55931c11877be74d1a5de958f67893c

May 09 02:23:43 fleximi-web dockerd[12595]: time="2018-05-09T02:23:43Z" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/0c08aca4930ff5fade2a035bc94d27a2070090c2e
May 09 02:24:23 fleximi-web dockerd[12595]: time="2018-05-09T02:24:23Z" level=info msg="shim reaped" id=0c08aca4930ff5fade2a035bc94d27a2070090c2eabefb1b941db1c8c63c1a25 module="containerd/tasks"
May 09 02:24:23 fleximi-web dockerd[12595]: time="2018-05-09T02:24:23.775065468Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
May 09 02:25:02 fleximi-web dockerd[12595]: time="2018-05-09T02:25:02Z" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/7534e4bbc909688ae4c399a03f65ae29480ca6ef2
May 09 02:25:02 fleximi-web dockerd[12595]: time="2018-05-09T02:25:02Z" level=info msg="shim reaped" id=7534e4bbc909688ae4c399a03f65ae29480ca6ef26276991cdf46741541a2172 module="containerd/tasks"
May 09 02:25:02 fleximi-web dockerd[12595]: time="2018-05-09T02:25:02.464189982Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
May 09 02:26:39 fleximi-web dockerd[12595]: time="2018-05-09T02:26:39Z" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/3d3c041194ff21f471510239c772f9242a168beb2
May 09 02:27:18 fleximi-web dockerd[12595]: time="2018-05-09T02:27:18Z" level=info msg="shim reaped" id=3d3c041194ff21f471510239c772f9242a168beb236209ddb77150a71001c538 module="containerd/tasks"
May 09 02:27:18 fleximi-web dockerd[12595]: time="2018-05-09T02:27:18.115069679Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
May 09 02:31:39 fleximi-web dockerd[12595]: time="2018-05-09T02:31:39Z" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/b3cb5382bc33af67787cd67bef26e55931c11877b

I want to try running it in https://vps_ip_address:8083

mysql fail start

Hi,
When i trying to run the image with yml, i m getting this, rest of log is good.

Starting MariaDB database server mysqld
   ...fail!

After that, container runs up, but i cant start mysql. Mysql error logs show nothing.
Any help?

Edit :
On my last test your YML file is working good but mine is not. After containers up, mysql is not working.

version: "3.7"
services:
  vcp:
    image: niiknow/vestacp
    hostname: ABWB
    volumes:
      - type: volume
        source: vesta-backup
        target: /backup
        volume:
          nocopy: true
      - type: volume
        source: vesta-vesta
        target: /vesta
        volume:
          nocopy: true
      - type: volume
        source: vesta-home
        target: /home
        volume:
          nocopy: true
    ports:
      - "3322:22"
      - "80:80"
      - "443:443"
      - "9088:8083"
    labels:
      - "Vesta Control Panel"
    deploy:
      mode: replicated
      replicas: 2
      restart_policy:
        condition: any
        delay: 10s
        max_attempts: 10
volumes:
  vesta-backup:
  vesta-vesta:
  vesta-home:

Edit 2:

I think i found the problem, it is about replicas size. 1 Replica is working good, more is not.
When i incrise replica size more than 1, mysql not starting.

Any help?

Problem with different host IP

I'm following this project for days. I'm trying to make this work in production with no success.

That's my current docker-compose.file:

version: "2"   # I added version '2' to add more compatibility, my docker doesn't support it.

services:
  vesta:
    image: niiknow/vestacp:0.9.27
    container_name: vesta
    volumes:
      - "./vestacp/backup:/backup"
      - "./vestacp/vesta:/vesta"    
      - "./vestacp/home:/home"
    ports:
      - "54.39.3.6:22:22" # This is how I bind the IP. I do it with all the rest of services and works.
      - "54.39.3.6:80:80" # I simply add the IP's in /etc/network/interfaces on the host server.
      - "54.39.3.6:443:443"
      - "54.39.3.6:8083:8083"
    cap_add: ['NET_RAW', 'NET_ADMIN']
    environment:
      - "VESTA_DOMAIN=hosting.example.com"
    labels:
      - "Vesta Control Panel"
    restart: unless-stopped

In first instance I get this error running the docker-compose:

root@srv01:/home/compose/hosting(master⚡) # docker-compose up
Recreating vesta
Attaching to vesta
vesta    | *** Running /etc/my_init.d/startup.sh...
vesta    | [i] running /home/admin/bin/my-startup.sh
vesta    | bash: /home/admin/bin/my-startup.sh: No such file or directory
vesta    | [i] running /bin/vesta-auto-ssl.sh
vesta    | [err] Domain 'hosting.xscru.com' IP '54.39.3.6' does not match Host IP '37.58.28.82'
vesta    | *** Running /etc/rc.local...
vesta    | *** Booting runit daemon...

I went into the file and removed the IP check and it worked.

Problems starts when I try to attach new IP's to the container. How I achieve this point?

Maintenance

Hi,
awesome, thx for your great work. I'm testing out your image and wonder if you plan to maintain this in the future?
There is a new VestaCP version planned soon :)
@noogen

The server is running, but fails to accept the SSH connection.

Command

ssh -p 2222 -v [email protected]

Debug info

OpenSSH_7.3p1, LibreSSL 2.4.1 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 20: Applying options for * debug1: Connecting to 0.0.0.0 [0.0.0.0] port 2222. debug1: Connection established. debug1: identity file /Users/[user]/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /Users/[user]/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/[user]/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/[user]/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/[user]/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/[user]/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/[user]/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/[user]/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.3 ssh_exchange_identification: Connection closed by remote host

OS
Mac OS X Sierra

Docker Version
1.12.5

Admin UI down using specific IP

Hello,

Installed the using docker-compose as per the instructions, modified the yml as follows.

However the 8083 port is not open, I'm assigning a specific IP to the forwarded ports, anything else I can do to enable the admin interface??

Thanks in advance

version: "2"

services:
  vesta:
    image: niiknow/vestacp
    container_name: vesta
    volumes:
      - "/data1/vestacp/backup:/backup"
      - "/data1/vestacp/vesta:/vesta"
      - "/data1/vestacp/home:/home"
    ports:
      - "8.8.8.8:2222:22"
      - "8.8.8.8:2121:21"
      - "8.8.8.8:53:53"
      - "8.8.8.8:81:80"
      - "8.8.8.8:444:443"
      - "8.8.8.8:3307:3306"
      - "8.8.8.8:8083:8083"
    privileged: true
    labels:
      - "Vesta Control Panel"
    restart: unless-stopped

    networks:
      vesta_network1:
        ipv4_address: 172.54.54.2
networks:
  vesta_network1:
    driver: bridge
    ipam:
      config:
        - subnet: 172.54.54.0/24
          gateway: 172.54.54.1

Not able to get VestaCP working

Running clean docker deployment with:
mkdir -p /opt/vestacp/{vesta,home,backup} && docker run -d --restart=always -p 80:80 -p 443:443 -p 8083:8083 -v /opt/vestacp/vesta:/vesta -v /opt/vestacp/home:/home -v /opt/vestacp/backup:/backup niiknow/vestacp

VESTA_DOMAIN environment variable was not set for test.

Port 8083 is not listened by nginx inside container.
Also notice line 473 in Dockerfile:
nginx-vesta should be vesta-nginx as it is stated on line 16 of /etc/init.d/vesta inside container.
Even if I rename nginx-vesta to vesta-nginx in /usr/local/vesta/nginx/sbin/, I can't get it to listen on 8083, but get following errors:

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 127.0.0.1:8084 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 127.0.0.1:8084 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 127.0.0.1:8084 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 127.0.0.1:8084 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 127.0.0.1:8084 failed (98: Address already in use)
nginx: [emerg] still could not bind()

Delete default domain

I see this error when I try to delete the default domain. Is it possible?

"Error: Parsing error"

In vesta logs I see

/var/log/vesta/error.log

2018-12-28 13:54:58 v-delete-web-domain  'admin' 'mydomain-.com' 'no' [Error 12]
2018-12-28 13:54:58 v-delete-domain  'admin' 'mydomain.com' [Error 12]

Thanks,

I can't start from docker-compose (postgres fails)

Every time I attempt to start from docker-compose up I get a permissions error with postgres starting:

image
This seems to stop the remaining services from starting also.

Here's my compose file:

version: "3.3"

services:
  vesta:
    image: niiknow/vestacp:1.1.6
    container_name: vesta
    volumes:
      - "./data/vestacp/backup:/backup"
      - "./data/vestacp/vesta:/vesta"
      - "./data/vestacp/home:/home"
    ports:
      - "2222:22"
      - "80:80"
      - "443:443"
      - "8083:8083"
    labels:
      - "Vesta Control Panel"
    restart: unless-stopped

phpMyAdmin not work

I has installed 1.8.1,but phpMyAdmin not work correctly ,show error
"403
Forbidden
Unfortunately, you do not have permission to view this"

Error when build

When I try to build I get this error message:

[...]
Reading package lists...
W: GPG error: http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.6 Release: The following signatures were invalid: KEYEXPIRED 1544811256
W: The repository 'http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.6 Release' is not signed.
E: Failed to fetch store:/var/lib/apt/lists/partial/repo.mongodb.org_apt_ubuntu_dists_xenial_mongodb-org_3.6_multiverse_binary-amd64_Packages.gz  Hash Sum mismatch
E: Some index files failed to download. They have been ignored, or old ones used instead.
Error executing command, exiting
tail: cannot open 'debian/changelog' for reading: No such file or directory
dpkg-buildpackage: error: tail of debian/changelog gave error exit status 1
[...]

AWStats Error

After enable AWStats for a website, I got this error:

Error: LogFile parameter is not defined in config/domain file 

Setup ('/etc/awstats/conf' file, web server or permissions) may be wrong.
Check config file, permissions and AWStats documentation (in 'docs' directory).

There is a little question that /etc/awstats folder only include these file:

awstats.conf  awstats.conf.local  awstats.abc.com.conf

Do you have any advise about this?

1.8.3: can't retrieve Letsencrypt certs

It seems to be VestaCP issue, but may be not:

At the start of container i have:

[i] running /bin/vesta-auto-ssl.sh
[i] Creating cert for 'admin' domain 'mydomain.nl'
Error: Let's Encrypt new auth status 429
[err] cert not found '/home/admin/conf/web/ssl.mydomain.nl.pem'

It works well in vestacp:latest image.

Also, I'cant get certs for any domain I added:

Error: Let's Encrypt validation status 400

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.