Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

synology wordpress setup error #319

Open
chqzeng opened this issue Oct 29, 2023 · 0 comments
Open

synology wordpress setup error #319

chqzeng opened this issue Oct 29, 2023 · 0 comments

Comments

@chqzeng
Copy link

chqzeng commented Oct 29, 2023

Hi all, very new to this topic and try to follow the steps here to setup a wordpress on SYNOLOGY.
what I have done:

  • setup hardware (DS1520+), install docker (now container manager), install docker compose, SSH , file permission to user, and firewall allow ports
  • git clone this project into my docker folder: /volume2/docker/docker-traefik, modify the .env with values:
PUID=1026
PGID=100
TZ=America/New York
USERDIR=/volume2/homes/LocalUser
DOCKERDIR=/volume2/docker/docker-traefik
SECRETSDIR=/volume2/docker/docker-traefik/secrets
SERVER_IP=
PIHOLE_IP=
LOCAL_NETWORK=
LOCAL_IPS=127.0.0.1/32,10.0.0.0/8,192.168.0.0/16,172.16.0.0/12
  • direct run: sudo docker-compose -f ./docker-compose-t2-synology.yml up -d , failed with many errors;
  • shorten the docker-compose-t2-synology.yml file, only keep
network: 
     .... all default values ....
service: 
   traefik:
     .... default value remove secret ...
    ...(default ports) ...
    ports:
      - target: 80
        published: 80
        protocol: tcp
        mode: host
      - target: 443
        published: 443
        protocol: tcp
        mode: host
      - target: 8080 # insecure api wont work
        published: 8085
        protocol: tcp
        mode: host

and re-run: sudo docker-compose -f ./docker-compose-t2-synology.yml up -d , with output:

WARN[0000] The "DOMAINNAME_HOME_SYNOLOGY" variable is not set. Defaulting to a blank string. 
WARN[0000] The "DOMAINNAME_HOME_SYNOLOGY" variable is not set. Defaulting to a blank string. 
WARN[0000] The "DOMAINNAME_HOME_SYNOLOGY" variable is not set. Defaulting to a blank string. 
[+] Building 0.0s (0/0)                                                                                                                                                                             docker:default
[+] Running 4/4
 ✔ Network socket_proxy    Created                                                                                                                                                                            0.1s 
 ✔ Network t2_proxy        Created                                                                                                                                                                            0.1s 
 ✔ Container socket-proxy  Started                                                                                                                                                                            0.0s 
 ✔ Container traefik       Created                                                                                                                                                                            0.0s 
Error response from daemon: driver failed programming external connectivity on endpoint traefik (44a534cb26099780ae5663e31f2840fe12280f1ba0f357bb5748d0aa52010f04): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use

and here is the log file, when run : sudo docker-compose -f ./docker-compose-t2-synology.yml logs

WARN[0000] The "DOMAINNAME_HOME_SYNOLOGY" variable is not set. Defaulting to a blank string. 
WARN[0000] The "DOMAINNAME_HOME_SYNOLOGY" variable is not set. Defaulting to a blank string. 
WARN[0000] The "DOMAINNAME_HOME_SYNOLOGY" variable is not set. Defaulting to a blank string. 
socket-proxy  | [WARNING] 301/022402 (1) : Can't open server state file '/var/lib/haproxy/server-state': No such file or directory
socket-proxy  | Proxy dockerbackend started.
socket-proxy  | Proxy dockerfrontend started.
socket-proxy  | [NOTICE] 301/022402 (1) : New worker #1 (7) forked

here are questions:

  • what is the meaning of this "bind: address already in use" error?
  • what IP access:port do I need to access the wordpress page from my local machine (not within synology where there is no browser)?
  • do I need to setup this "DOMAINNAME_HOME_SYNOLOGY" ? I plan to migrate my wordpress from a cloud host (xxxx.com)
  • what would be the best way to migrate from cloud server to sysnology wordpress?

thank you,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant