Skip to main content

FAQ

Frequently Asked Installation Questions​

  1. Does WeDa private deployment support Windows?​

    Not supported. Please refer to the installation Machine Configuration Requirements.

  2. Can the license be used multiple times?​

    The license can only be activated on one cvm. If it has been activated on another cvm, it cannot be activated again on the current cvm.

  3. Activation as shown in the following prompts​

    alt text

    Please go to Renew license.

  4. Does the private deployment version upgrade affect existing business data?​

    No impact. Please follow the upgrade steps: Version Upgrade.

  5. Did the installation fail because the server does not have an https certificate?​

    You can use the command: wget --no-check-certificate http://xxxx to skip SSL/TLS certificate verification.

  6. Should the installation allow specifying a pure intranet ip as the access address?​

    By default, public IP is used for access. Refer to Port Number and Allowlist IP Configuration to specify an intranet IP: http://xxx.xxx.x.x:80 (protocol, address, port).

  7. After customizing the MySQL configuration, restarting the platform service prompts Access denied​

    alt text

    Check whether the MySQL information entered in the config.yaml file can be connected from the current machine.

  8. Installation error shows: "Conflict. The container name \"/mysql\" is already in use by container"​

  • Analysis: This error indicates that a docker container named "mysql" already exists on the current vm
  • Solution:

  1. Installation error shows: "Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use"​

  • Analysis: This error indicates that port 80 on the current vm is already occupied, so WeDa cannot use port 80.
  • Solution:
    • 9.1. Stop the service currently using port 80
    • 9.2. Go to the installation configuration page -> Access Address -> fill in the correct access address and an unused port

  1. Installation error shows: "exec the task failed :WEDA STEP 5: clean up, Warning Configuration file /data/tencent/weda/docker-compose.yaml not found. Skipping docker-compose command."​

  • Analysis: This error indicates that some services have not been stopped during the current clean-up process.
  • Solution:
    • 10.1. Stop the currently running services by executing docker ps -q | xargs -r docker stop, then reinstall.

  1. Installation error shows: "Cannot connect to the Docker daemon at unix:/ //var/run/docker.sock. Is the docker daemon running?"​

  • Analysis: docker is installed on the server, but the service has not been started.
  • Solution:
    • 11.1. Run: sudo systemctl start docker
    • 11.2. sudo systemctl enable docker

  1. Installation error: "WEDA STEP O: install docker Docker is not installed, starting to install Docker using yum"​

  • Analysis: The download may fail during yum installation on the server because the yum repository lacks the required resources.
  • Solution:
    • Change the image source for manual installation. Refer to the documentation: Set up Docker

  1. Error in init-env during installation​

  • Analysis: Custom mysql (version 8.0 or above) incompatibility causes the error, Logs: docker logs -f init-env

  • Solution:

If the external mysql is configured as follows, it can be processed.


[client]
default_character_set = utf8mb4

[mysql]
default-character-set=utf8mb4

[mysqld]
character-set-server=utf8mb4
collation-server=utf8mb4_unicode_ci
sql_mode = ALLOW_INVALID_DATES
explicit_defaults_for_timestamp = OFF

  1. When executing cluster deployment, the following error is reported. Please check the license type; currently only the Enterprise Edition is supported.​

    alt text

  1. Can the File/Image Upload Component also support uploading to custom storage buckets?​

    Yes. Please refer to the Custom S3 Object Configuration Guide.

  2. What are the capability differences between the WeDa private deployment edition and the public cloud edition?​

    Please refer to the Capability Comparison List for differences in capabilities.