Re: SUPLA i SUPLA Scripts na jednej maszynie (docker proxy)
: ndz mar 18, 2018 8:30 pm
Podaj adres:81 czyli adres dwukropek i port jaki ustawiłeś.
Kod: Zaznacz cały
root@orangepizero:~# docker logs --since=5m supla-cloud 2018-06-02 14:30:21,112 WARN received SIGTERM indicating exit request 2018-06-02 14:30:21,146 INFO waiting for apache, cron to die 2018-06-02 14:30:21,158 INFO stopped: cron (terminated by SIGTERM) [Sat Jun 02 14:30:22.564659 2018] [mpm_prefork:notice] [pid 50] AH00169: caught SIGTERM, shutting down 2018-06-02 14:30:22,697 INFO stopped: apache (exit status 0) Database connection has been established. Application Migrations No migrations to execute. // Warming up the cache for the prod environment with debug // false [OK] Cache for the "prod" environment (debug=false) was successfully warmed. User firstname.lastname@example.org already exists. 2018-06-02 14:31:54,643 CRIT Supervisor running as root (no user in config file) 2018-06-02 14:31:54,671 INFO supervisord started with pid 1 2018-06-02 14:31:55,679 INFO spawned: 'apache' with pid 49 2018-06-02 14:31:55,689 INFO spawned: 'cron' with pid 50 2018-06-02 14:31:56,693 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-06-02 14:31:56,694 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.5. Set the 'ServerName' directive globally to suppress this message [Sat Jun 02 14:31:56.763133 2018] [ssl:warn] [pid 49] AH01906: 172.20.0.5:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?) [Sat Jun 02 14:31:56.763459 2018] [ssl:warn] [pid 49] AH01909: 172.20.0.5:443:0 server certificate does NOT include an ID which matches the server name AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.5. Set the 'ServerName' directive globally to suppress this message [Sat Jun 02 14:31:57.447351 2018] [ssl:warn] [pid 49] AH01906: 172.20.0.5:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?) [Sat Jun 02 14:31:57.447593 2018] [ssl:warn] [pid 49] AH01909: 172.20.0.5:443:0 server certificate does NOT include an ID which matches the server name [Sat Jun 02 14:31:57.472974 2018] [mpm_prefork:notice] [pid 49] AH00163: Apache/2.4.10 (Debian) PHP/7.0.26 OpenSSL/1.0.1t configured -- resuming normal operations [Sat Jun 02 14:31:57.473157 2018] [core:notice] [pid 49] AH00094: Command line: 'apache2 -D FOREGROUND'
Kod: Zaznacz cały
# # docker-compose-letsencrypt-nginx-proxy-companion # # A Web Proxy using docker with NGINX and Let's Encrypt # Using the great community docker-gen, nginx-proxy and docker-letsencrypt-nginx-proxy-companion # # This is the .env file to set up your webproxy enviornment # # Your local containers NAME # NGINX_WEB=nginx-web DOCKER_GEN=nginx-gen LETS_ENCRYPT=nginx-letsencrypt # # Your external IP address # IP=0.0.0.0 # # Default Network # NETWORK=webproxy # # Service Network (Optional) # # In case you decide to add a new network to your services containers you can set this # network as a SERVICE_NETWORK # # [WARNING] This setting was built to use our `start.sh` script or in that special case # you could use the docker-composer with our multiple network option, as of: # `docker-compose -f docker-compose-multiple-networks.yml up -d` # #SERVICE_NETWORK=webservices # # NGINX file path # NGINX_FILES_PATH=/path/to/your/nginx/data # # NGINX use special conf files # # In case you want to add some special configuration to your NGINX Web Proxy you could # add your files to ./conf.d/ folder as of sample file 'uploadsize.conf' # # [WARNING] This setting was built to use our `start.sh`. # # [WARNING] Once you set this options to true all your files will be copied to data # folder (./data/conf.d). If you decide to remove this special configuration # you must delete your files from data folder ./data/conf.d. # #USE_NGINX_CONF_FILES=true # # Docker Logging Config # # This section offers two options max-size and max-file, which follow the docker documentation # as follow: # # logging: # driver: "json-file" # options: # max-size: "200k" # max-file: "10" # #NGINX_WEB_LOG_MAX_SIZE=4m #NGINX_WEB_LOG_MAX_FILE=10 #NGINX_GEN_LOG_MAX_SIZE=2m #NGINX_GEN_LOG_MAX_FILE=10 #NGINX_LETSENCRYPT_LOG_MAX_SIZE=2m #NGINX_LETSENCRYPT_LOG_MAX_FILE=10
Kod: Zaznacz cały
/ __| | | | _ \ | /_\ \__ \ |_| | _/ |__ / _ \ |___/\___/|_| |____/_/ \_\ / __| __ _ _(_)_ __| |_ ___ \__ \/ _| '_| | '_ \ _(_-< |___/\__|_| |_| .__/\__/__/ |_| by @fracz v2.8.0 The encryption key already exists. No changes made. Cache has been cleared successfully mysqldump: Error: 'Access denied for user 'suplascripts'@'%' (using password: YES)' when trying to dump tablespaces Could not make the database backup. Phinx by Rob Morgan - https://phinx.org. 0.8.1 using config file ./backend/database/phinx-config.php using config parser php using migration paths - /var/www/backend/database/migrations using seed paths warning no environment specified, defaulting to: db using adapter mysql using database suplascripts [InvalidArgumentException] There was a problem connecting to the database: SQLSTATE[HY000]  The server requested authentication method unknown to the client migrate [-c|--configuration CONFIGURATION] [-p|--parser PARSER] [-e|--environment ENVIRONMENT] [-t|--target TARGET] [-d|--date DATE]