-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Axios can't access static.etherpad.org but Docker Container can #6475
Comments
This is 100% on your side... |
I would have thought so but I can't think of what networking or firewall configuration would impact the node app but not impact curl when they're both running inside the same container. Can you? |
I'm not a network expert ... all I can suggest is try a different machine on a different network. |
Did you find the solution? |
No, Docker is doing it's own management of IPTables, which hasn't introduced any rules that I could see would interfere, and nothing between the Docker host and the internet is interfering (Eg: IPS). Whilst it hasn't impacted core functionality, it's a bit frustrating. We're considering moving to cryptpad instead because it has native support for SSO (with a plugin at least) which fits our use-case better anyway. I guess if no one else has this issue, one could close it. |
It seems that diff --git a/src/node/server.ts b/src/node/server.ts
index f96db3ab..edb687d7 100755
--- a/src/node/server.ts
+++ b/src/node/server.ts
@@ -29,6 +29,13 @@ import pkg from '../package.json';
import {checkForMigration} from "../static/js/pluginfw/installer";
import axios from "axios";
+axios.head('https://static.etherpad.org/plugins.json').catch(() => {
+ const http = require('http');
+ const https = require('https');
+ axios.defaults.httpAgent = new http.Agent({ family: 4 });
+ axios.defaults.httpsAgent = new https.Agent({ family: 4 });
+});
+
const settings = require('./utils/Settings');
let wtfnode: any; |
@eternalphane You were able to reproduce this issue? I wonder why others have not encountered this problem. Should this perhaps be spun out into a toggle/environmental variable? |
I'm wondering why this should be the case. I'll try that patch. Maybe you can too @Viajaz if you are still considering Etherpad. |
@Viajaz @SamTV12345 I just happened to come across this issue when I deployed etherpad in a dev cluster which I forgot to enable IPv6 support |
|
Our environment hasn't and doesn't support IPv6 and it's routing. |
Then it may be that your DNS is not returning the IPv6 address of |
Fixed you can now add your own server like https://etherpad.org/ep_infos |
Describe the bug
Node app (Axios) can't access online network resources (
static.etherpad.org
) despite other tools (eg:curl
) being able to inside same container.To Reproduce
docker-compose.yml
Expected behavior
Functioning network access.
Screenshots
However, I can go into the docker container and run curl just fine.
The text was updated successfully, but these errors were encountered: