search

inovector / mixpost

Mixpost - Self-hosted social media management software (Buffer alternative)
https://mixpost.app
MIT License
1.19k stars 183 forks source link

Fresh Docker Install in Windows Server 2022 #103

Open SFARPak opened 5 months ago

SFARPak commented 5 months ago

Steps to reproduce the problem

  1. Installed Docker Desktop in Windows Server 2022
  2. Created docker-compose.yaml
  3. Started containers with docker-compose up -d
  4. Mixpost starts successfully in logs but there is some FATA state error as shown below.

Expected behaviour

App Should run

Actual behaviour

FATAL ERROR

Detailed description

2024-06-13 15:16:42 mixpost-1 | ------- Mixpost has started! ------- 2024-06-13 15:16:42 mixpost-1 | 2024-06-13 10:16:42,400 INFO Set uid to user 0 succeeded 2024-06-13 15:16:42 mixpost-1 | 2024-06-13 10:16:42,402 INFO supervisord started with pid 82 2024-06-13 15:16:43 mixpost-1 | 2024-06-13 10:16:43,406 INFO spawned: 'mixpost_horizon_00' with pid 84 2024-06-13 15:16:43 mixpost-1 | 2024-06-13 10:16:43,410 INFO spawned: 'nginx' with pid 85 2024-06-13 15:16:43 mixpost-1 | 2024-06-13 10:16:43,413 INFO spawned: 'php-fpm' with pid 86 2024-06-13 15:16:43 mixpost-1 | 2024-06-13 10:16:43,463 INFO exited: mixpost_horizon_00 (exit status 255; not expected) 2024-06-13 15:16:44 mixpost-1 | 2024-06-13 10:16:44,471 INFO spawned: 'mixpost_horizon_00' with pid 109 2024-06-13 15:16:44 mixpost-1 | 2024-06-13 10:16:44,472 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-06-13 15:16:44 mixpost-1 | 2024-06-13 10:16:44,472 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-06-13 15:16:44 mixpost-1 | 2024-06-13 10:16:44,526 INFO exited: mixpost_horizon_00 (exit status 255; not expected) 2024-06-13 15:16:46 mixpost-1 | 2024-06-13 10:16:46,531 INFO spawned: 'mixpost_horizon_00' with pid 110 2024-06-13 15:16:46 mixpost-1 | 2024-06-13 10:16:46,576 INFO exited: mixpost_horizon_00 (exit status 255; not expected) 2024-06-13 15:16:49 mixpost-1 | 2024-06-13 10:16:49,582 INFO spawned: 'mixpost_horizon_00' with pid 111 2024-06-13 15:16:49 mixpost-1 | 2024-06-13 10:16:49,648 INFO exited: mixpost_horizon_00 (exit status 255; not expected) 2024-06-13 15:16:50 mixpost-1 | 2024-06-13 10:16:50,649 INFO gave up: mixpost_horizon_00 entered FATAL state, too many start retries too quickly

Specifications

Mixpost v1.7.0 Windows Server 2022

chrisbehectik commented 5 months ago

I get the same thing running Debian Bookworm on a Rasp Pi 5 4GB. Fresh install.

chrisbehectik commented 5 months ago

@SFARPak Can you share your docker compose file?

I would like to compare.

Initially I had mounted volume from local directories which gave me the same error as you. After changing to the default in MixPost's documentation I no longer got that issue but ran into another one.

lao9s commented 3 months ago

I think the mixpost service can't communicate with MySQL service. Have you used our docker-compose.yml example? https://docs.mixpost.app/lite/installation/docker#3-create-docker-compose-file

morvy commented 2 months ago

Had the same issue, but I removed the traefik part, because I have my own instance ..and forgot to create a separate network for internal communication, where mysql and redis instances are accessible. (It didn't solve the issue, but my DB is accessible from mixpost instance) EDIT: it did solve the issue, I just had to delete mysql volume and start again as the user/pass I used was different..