-
Notifications
You must be signed in to change notification settings - Fork 247
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
Run-TestsInBcContainer on NextMajor containers results in a SSL connection error #3812
Comments
We've found some similar issues:
If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.
|
See also: Run-TestsInBCContainer Running 401 (Unauthorized) [https://github.com//issues/3783] |
Have you tried this without traefik? |
Hi Freddy, Is the absence of Traefik in the builds of newer versions planned by design, or is it a temporary technical issue? |
Absence of Traefik??? - not sure what you are referring to. I was just asking whether this was a traefik problem or it was caused by something else. |
Seems to be issue with Traefik since NextMajor builds now work fine with Traefik disabled. All builds prior to 26.0.25383.0/26.0.25330.0 were running with Traefik enabled and there were no issues. |
I disagree - Traefik hasn't changed - BC has changed. |
I was able to log via Web Client with Traefik active (NextMajor Version: W1 26.0 - Platform 26.0.29477.0 + Application 26.0.29555.0). Let me know if you need anything else. |
Describe the issue
Since November 2024, we've been encountering issues with running tests in containers based on NextMajor artifacts. Last successful run was on versions 26.0.25383.0/26.0.25330.0 (BC version/platform version). Currently, we're receiving CommunicationError: The SSL connection could not be established. App publishing and compilation runs fine (these steps are run prior to testing).
Please note that we haven't made any changes in our build scripts in the last year.
Scripts used to create container and cause the issue
Full output of scripts
Screenshots
Additional context
Yes, ever since November of 2024.
Yes.
The text was updated successfully, but these errors were encountered: