Discussions

Ask a Question
Back to All

MetaProxy is not running.

MetaProxy is not running.

I have already tried restarting and followed the guide but to no avail.

From what I can see from the logs it would appear to be a fault on your end and i can see that there are no Active Forging tickets from today.

From log file, if it helps.

02 05.15_14:03:18 WSP: 0
02 05.15_14:03:18 WSP: Wss Web socket error Invalid statusline in response:

.wss://wss4.metahashnetwork.com
02 05.15_14:03:18 WSP: 0
02 05.15_14:03:18 WSP: Wss Web socket error Invalid statusline in response: 502 Bad Gateway

.wss://wss4.metahashnetwork.com
02 05.15_14:03:18 WSP: 0
02 05.15_14:03:18 WSP: Wss Web socket error Invalid statusline in response:

.wss://wss4.metahashnetwork.com
02 05.15_14:03:18 WSP: 0
02 05.15_14:03:18 WSP: Wss Web socket error Invalid statusline in response:

502 Bad Gateway

.wss://wss4.metahashnetwork.com
02 05.15_14:03:18 WSP: 0
02 05.15_14:03:18 WSP: Wss Web socket error Invalid statusline in response:


nginx/1.14.0 (Ubuntu)

.wss://wss4.metahashnetwork.com
02 05.15_14:03:18 WSP: 0
02 05.15_14:03:18 WSP: Wss Web socket error Invalid statusline in response:

.wss://wss4.metahashnetwork.com
02 05.15_14:03:18 WSP: 0
02 05.15_14:03:18 WSP: Wss Web socket error Invalid statusline in response:

.wss://wss4.metahashnetwork.com
00 05.15_14:03:20 : Status command
01 05.15_14:03:22 WSS: Wss client onStarted. Url wss://wss.osenyndab.com/
01 05.15_14:03:23 WSS: Wss Web socket error Invalid statusline in response:

. wss://wss.osenyndab.com/
01 05.15_14:03:23 WSS: Wss client disconnected. Url wss://wss.osenyndab.com/

Sorry for double post but it seem that by adding a comment would mark it as answering the question.