4.4.7 Docker-compose install failing with error message

Questions
1

Hello,

I previously reported this as a bug. It was closed, so I’m asking this as a question.

the app container keeps restarting with the below error message

app_1                  | /opt/mayan-edms/lib/python3.9/site-packages/requests/__init__.py:102: RequestsDependencyWarning: urllib3 (1.26.16) or chardet (5.1.0)/charset_normalizer (2.0.12) doesn't match a supported version!
app_1                  |   warnings.warn("urllib3 ({}) or chardet ({})/charset_normalizer ({}) doesn't match a supported "
app_1                  | Error checking Celery broker connectivity: Port could not be cast to integer value as 'Kvp45AXU'

I was told this is an error on my part, but I don’t know what I could have done to affect this. I’m using the provided docker-compose file. I added a network for my existing reverse proxy, and edited the .env file with passwords and data volume locations.

Thanks for any help.

2

Greetings,

The error is caused by your edits. It says so in the message.

Error checking Celery broker connectivity: Port could not be cast to integer value as 'Kvp45AXU'

It is expecting a port number but you entered “Kvp45AXU”.

BTW your previous topic was probably closed because you omitted the fact that you modified the installation file. Instead filed it as a bug of urllib3 making the mayan people and forum members waste time looking for an error that did not existed trying to help you.

Using the search function for “urllib3” this is found in another conversation.

The warnings about urllib3, chardet and charset_normalizer are normal and are cause by the transition between Python 3.9 and 3.10 taking place for some dependencies.

Also your reaction to being corrected.

3

I have no Port defined as “Kvp45AXU”. I did not modify any port settings at all in the docker-compose.yml file.

Again, What was modified, I’ve already described in the initial post.

4

This problem has been solved.

One of the passwords setup in the .env file had a # character and that caused docker-compose to misread the file and insert part of the password in the Port setting that used a variable in the docker-compose.yml file.