workers connect fail

[qutimqqcom]

setup new using docker

Already up to date.
audited 430 packages in 11.316s
found 17 vulnerabilities (4 low, 10 moderate, 3 high)
run npm audit fix to fix them, or npm audit for details
Proxy updated OK! Please go ahead and restart with the correct pm2 command
This is usually pm2 restart proxy, however, you can use pm2 list to check for your exact proxy command
Xmr-Node-Proxy (XNP) v0.3.0
Cluster master setting up 4 workers...
Activating Web API server on 0.0.0.0:8081
Worker 39 is online
Worker 45 is online
Worker 33 is online
Worker 38 is online
[MASTER] Connected to pool: de.moneroocean.stream
Received new block template on 1663939 height (algo: cn/1, variant: 1) with 2000 target difficulty from de.moneroocean.stream

BUT workers get error during connect

• VERSIONS XMRig/2.6.4 libuv/1.8.0 gcc/5.5.0
• CPU Intel(R) Xeon(R) CPU E5-2623 v3 @ 3.00GHz (1) x64 AES-NI
• CPU L2/L3 1.0 MB/10.0 MB
• THREADS 4, cryptonight, av=0,
• POOL no aes-ni #1 IP:PORT variant 1
• COMMANDS hashrate, pause, resume
  [2018-09-18 12:52:48] READY (CPU) threads 4(4) huge pages 4/4 100% memory 8.0 MB
  [2018-09-18 12:52:48] [IP:PORT] error: "Invalid address used for login", code: -1
  [2018-09-18 12:52:52] Ctrl+C received, exiting

[djfinch]

Repo's Dockerfile copying config_example.json to config.json...
https://github.com/MoneroOcean/xmr-node-proxy/blob/master/Dockerfile#L12
This is correct Dockerfile which copy your config.json to container...
config.json needs to be stored in the folder with Dockerfile...
https://github.com/djfinch/xmr-node-proxy-dev/blob/master/Dockerfile#L13

EDIT:
Change line 9 from
&& git clone https://github.com/djfinch/xmr-node-proxy /xmr-node-proxy \
to
&& git clone https://github.com/MoneroOcean/xmr-node-proxy /xmr-node-proxy \
(mine version is 1.6...)

[qutimqqcom]

no effect

[djfinch]

Ah, sorry... I missed that the error is from XMrig, not proxy itself...
config_example.json is shipped with

"accessControl": {
"enabled": false}

so this must be something with your miner config...

[qutimqqcom]

xmrig worker solo join pool success
xnp VM ubuntu join pool success /package.json: "version": "0.2.1", + xmrig connected to xnp join OK

when create using docker , get error
xnp connect to pool, but workers fail error: "Invalid address used for login", code: -1

{
"pools": [
{
"hostname": " pool ocean ",
"port": 10004,
"ssl": false,
"allowSelfSignedSSL": false,
"share": 100,
"username": "WALET.PAYID",
"password": "7:mail@post.ru",
"keepAlive": true,
"algo": "cryptonight/1",
"blob_type": "cryptonote",
"default": true
}

],
"listeningPorts": [
{
"port": 4444,
"ssl": false,
"diff": 4000
}
],
"bindAddress": "0.0.0.0",
"developerShare": 0,
"daemonAddress": "127.0.0.1:18081",
"accessControl": {
"enabled": false,
"controlFile": "accessControl.json"
},
"httpEnable": true,
"httpAddress": "0.0.0.0",
"httpPort": "8080",
"httpUser": "",
"httpPass": "",
"minerInactivityTime": 120,
"keepOfflineMiners": 0,
"refreshTime": 30,
"theme": "light",
"coinSettings": {
"xmr":{
"minDiff": 1000,
"maxDiff": 5000,
"shareTargetTime": 30
}
}
}

[djfinch]

This is config from docker instance? Or from working standalone XNP?
Have you added 4444 to exposed ports inside Dockerfile?
Looks OK to me (if pool ocean and WALET.PAYID is not literally there, indeed)...
Are you able to paste whole Dockerfile used to build your non-working instance?

[qutimqqcom]

yes, conf from docker,
port added during create
standalone using same WALET.PAYID

file

xmr-node-proxy-master # cat Dockerfile
FROM ubuntu:18.04

RUN apt-get update
&& apt-get install -y curl gnupg
&& curl -fsSL https://deb.nodesource.com/setup_8.x -o /tmp/node_setup.sh
&& bash /tmp/node_setup.sh
&& rm /tmp/node_setup.sh
&& apt-get install -y nodejs git make g++ libboost-dev libboost-system-dev libboost-date-time-dev
&& git clone https://github.com/MoneroOcean/xmr-node-proxy /xmr-node-proxy
&& cd /xmr-node-proxy
&& npm install
&& cp -n config_example.json config.json
&& openssl req -subj "/C=IT/ST=Pool/L=Daemon/O=Mining Pool/CN=mining.proxy" -newkey rsa:2048 -nodes -keyout cert.key -x509 -out cert.pem -days 36500

EXPOSE 8080 8443 3333

WORKDIR /xmr-node-proxy
CMD ./update.sh && node proxy.js

get here

https://github.com/MoneroOcean/xmr-node-proxy/archive/master.zip

raspberry pi 3

lscpu
Architecture: aarch64
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Model: 4
CPU max MHz: 1200.0000
CPU min MHz: 600.0000
BogoMIPS: 38.40
NUMA node0 CPU(s): 0-3
Flags: fp asimd evtstrm crc32

xmr-node-proxy-master # cat /etc/os-release
NAME="openSUSE Leap"
VERSION="42.3"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="42.3"
PRETTY_NAME="openSUSE Leap 42.3"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:42.3"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
rus-home:~/bin/xmr-node-proxy-master # uname -a
Linux rus-home 4.4.76-1-default #1 SMP Fri Jul 14 08:48:13 UTC 2017 (9a2885c) aarch64 aarch64 aarch64 GNU/Linux

docker -v
Docker version 17.09.1-ce, build f4ffd2511ce9

[djfinch]

Just tested current Dockerfile from repo and it works...
I cannot see exposed port 4444 in your Dockerfile.
cp -n config_example.json config.json will copy and use example config. Not your.
...

1. remove all of your previous XNP containers - docker ps -a and then docker rm container-ids
2. create empty folder mkdir ~/XNP then cd ~/XNP then nano Dockerfile and put below config inside (whole XNP is not needed, just Dockerfile)

FROM ubuntu:18.04

RUN apt-get update \
    && apt-get install -y curl gnupg \
    && curl -fsSL https://deb.nodesource.com/setup_8.x -o /tmp/node_setup.sh \
    && bash /tmp/node_setup.sh \
    && rm /tmp/node_setup.sh \
    && apt-get install -y nodejs git make g++ libboost-dev libboost-system-dev libboost-date-time-dev \
    && git clone https://github.com/MoneroOcean/xmr-node-proxy /xmr-node-proxy \
    && cd /xmr-node-proxy \
    && npm install \
    && openssl req -subj "/C=IT/ST=Pool/L=Daemon/O=Mining Pool/CN=mining.proxy" -newkey rsa:2048 -nodes -keyout cert.key -x509 -out cert.pem -days 36500
COPY config.json /xmr-node-proxy

EXPOSE 8080 8443 3333 4444

WORKDIR /xmr-node-proxy
CMD ./update.sh && node proxy.js

3. copy working config.json in the folder ~/XNP
4. run build docker build -t proxy . This will prepare the container and copy YOUR config inside
5. run docker run proxy

[qutimqqcom]

Just tested on linux server
same OS
Linux 4.17.12-1-default #1 SMP PREEMPT Fri Aug 3 06:36:01 UTC 2018 (ef4920c) x86_64 x86_64 x86_64 GNU/Linux
same Doccker
Docker version 17.09.1-ce, build f4ffd2511ce9

its work

maybe problem when based on

raspberry pi 3
lscpu
Architecture: aarch64

in close time reinstal OS on device aspberry pi 3

and post here results

THX for djfinch

[djfinch]

You're welcome. I missed that you're trying to use XNP on rPi... #32

I'm running proxy on x86_64 (Proliant Micro) and have just rPi2 but I can try it, too. Later...

[qutimqqcom]

OS
Linux 4.16.6-1-default #1 SMP Mon Apr 30 20:33:51 UTC 2018 (566acbc) aarch64 aarch64 aarch64 GNU/Linux
DOCKER
Docker version 17.09.1-ce, build f4ffd2511ce9

Get Error on worker side
xnp connect to pool, but workers fail error: "Invalid address used for login", code: -1

Docker build log attached
doc-build.log

Common CPU no problem (Intel(R) Xeon(R) CPU E5520 @ 2.27GHz)

[MoneroOcean]

Can you please show your config.json?

[qutimqqcom]

cat config.json
{
"pools": [
{
"hostname": "172.168.20.189",
"port": 6666,
"ssl": false,
"allowSelfSignedSSL": false,
"share": 100,
"username": "AmyowRbETtg47jo6EsqkcAAJAGjQ6RZHeumaifhzp8nQXEi7r5PyjaPHuRawPjRgqPXA6PzLe68Q1JzLM9V8bd48838c3b4093915b58d5b6651bb68b4027c542a019151144",
"password": "7:im@qq.com",
"keepAlive": true,
"algo": "cryptonight/1",
"blob_type": "forknote2",
"default": true
}

],
"listeningPorts": [
{
"port": 1004,
"ssl": false,
"diff": 2000
},
{
"port": 1006,
"ssl": false,
"diff": 2000
}
,{
"port": 1005,
"ssl": false,
"diff": 2000
}
,{
"port": 1001,
"ssl": false,
"diff": 2000
}
,{
"port": 1002,
"ssl": false,
"diff": 2000
}
,{
"port": 1009,
"ssl": false,
"diff": 2000
}
,{
"port": 1008,
"ssl": false,
"diff": 2000
}
,{
"port": 1007,
"ssl": false,
"diff": 2000
}
,{
"port": 1003,
"ssl": false,
"diff": 2000
}

],
"bindAddress": "0.0.0.0",
"developerShare": 0,
"daemonAddress": "127.0.0.1:18099",
"accessControl": {
"enabled": false,
"controlFile": "accessControl.json"
},
"httpEnable": true,
"httpAddress": "0.0.0.0",
"httpPort": "8099",
"httpUser": "",
"httpPass": "",
"minerInactivityTime": 120,
"keepOfflineMiners": 0,
"refreshTime": 30,
"theme": "light",
"coinSettings": {
"xmr":{
"minDiff": 1000,
"maxDiff": 5000,
"shareTargetTime": 30
}
}
}

[MoneroOcean]

Do you have EXPOSE 1001 1002 1003 1004 1005 1006 1007 1008 1009 in your Dockerfile?

[qutimqqcom]

port declare
docker create -p 1004:1004 ...... 1008:1008 --name xnp xmr-node-proxy