Skip to content
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

connect postgresql but cann't connect #53

Open
jameswangcnbj opened this issue Nov 1, 2017 · 3 comments · May be fixed by #74
Open

connect postgresql but cann't connect #53

jameswangcnbj opened this issue Nov 1, 2017 · 3 comments · May be fixed by #74

Comments

@jameswangcnbj
Copy link

i run i Run npx [email protected] in centos6.5 machine,and i got this message.
npx: 138 安装成功,用时 27.67 秒
franchise-client listening on port 14645

but in browse,the connect button is cann't use still, how to resolve it

@nicolkill
Copy link

i got the same bug, i run the franchise client and i dont get the connection

@senpl
Copy link

senpl commented Jun 29, 2018

In my case it connect well to the local mysql database, but not to the remote. So some part of remote database access might be blocked.

@psychemedia
Copy link

psychemedia commented Feb 2, 2019

I'm also getting a similar response when running franchise via the python simple http server start in franchise/bundle:

Connect the Database Bridge
Run npx [email protected] in your terminal to start the franchise database bridge.
If the npx command is not found, install the latest version of node and try again.
These instructions will automatically collapse as soon as the bridge is detected.

I started the bridge, and it seems to be running fine, but the message doesn't collapse.

Restarting the franchise server after starting the bridge service has the same result: the error message is still there.

Looking in browser console, I get error:

bridge.js:26 WebSocket connection to 'ws://localhost:14645/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

The offending line is:

clientConnectorSocket = new WebSocket(BRIDGE_URL);

with line 13 of the same file setting const BRIDGE_URL = 'ws://localhost:14645';

(See also #66 .)

My server is running on 127.0.0.1 rather than localhost. That shouldn't make a difference, right, unless there's an explicit string match going on somewhere?

If I start in franchise/ with yarn start I get an Invalid Host header error (see also: #61 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants