-
Notifications
You must be signed in to change notification settings - Fork 9
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
Failed to open stream: connection timed out, when use docker behind company proxy. #364
Comments
Hello, sorry for the delay in replying. If we can figure out how we can easily reproduce this in dev setups, then we can answer. |
Deployment Steps:
/etc/systemd/system/docker.service.d/http-proxy.conf
docker-compose.yaml
appapi config
After setting up according to the steps above, an error message pops up.
I have also tried to manually execute the app registration, but there is a similar error message.
I tried downloading the info.xml of test_deploy and specifying it directly, which can successfully register, but an error occurs when downloading the test_deploy image.
Error message:
P.S. When we download a file with https, we need skip certification verify. |
This is related to #371 I will update documentation for this, as the PROXY setting should be set for PHP CLI too and it should work after that. |
@aef5748 thanks for the explanation and patience. can you check if the linked pull request describes your situation and the suggested method fixes the installation for you? thanks for the advice |
Should resolve these installation issues: #364 and #371 Signed-off-by: Alexander Piskun <[email protected]>
I'm not sure if I have the settings correct, here are my steps:
Using method 2 to modify the environment file, the same result is obtained.
|
My nextcloud is setup on the docker behind company proxy.
After installed app_api then try to test_deploy, but got the following message:
Use Nextcloud to download others app successfully, so I think the network is workable.
How can I solved it?
NC: 29.0.3-apache
Appapi: 3.1.0
The text was updated successfully, but these errors were encountered: