You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Therefore I understood that in the docker-compose file I have to enable the “TLS” environment variable + add some credentials.
However when I open the Website using the https URL I am getting an error
When I configure my httpProxy to contact the AllureServer directly (e.g. to see the swagger page via https) it works. So the configuration of my httpProxy is correct.
It seems a problem in the AllureUI Implementation.
Also: I connected into the docker container of the AllureUI serice and could reach the AllureSrv container, via: curl https://allure_srv:5050/
So they do have a connection.
Hi !
I am facing the same error in a kubernetes setup : 1 namespace, 1 pod for the API, 1 for the UI
each pod has one docker container, allure folders are shared using Persistent Volume Claim.
The runAllureApp.sh script from allure-docker-service crashes after ~1hour
restarting the API pod manually makes it hold... and 1 hour later its the crash again.
Hi,
I have setup your Docker-Server + Docker-UI services and wanted to add an HTTPs server in front of it.
So basically:
[AllureSrv] <-- http --> [AllureUI] <-- http --> [httpProxy] <--- https (Internet)
Therefore I understood that in the docker-compose file I have to enable the “TLS” environment variable + add some credentials.
However when I open the Website using the https URL I am getting an error
When I configure my httpProxy to contact the AllureServer directly (e.g. to see the swagger page via https) it works. So the configuration of my httpProxy is correct.
It seems a problem in the AllureUI Implementation.
Also: I connected into the docker container of the AllureUI serice and could reach the AllureSrv container, via:
curl https://allure_srv:5050/
So they do have a connection.
Do you have an idea what I am doing wrong here?
This is my docker-compose file:
The text was updated successfully, but these errors were encountered: