patchy

I tried setting the popups in AJAX mode off or on, it didn’t fix it.

i have the same issue..

I tried it and it didn’t work..

I ended up setting a WP website on my vps and migrating it.
Now it works!

I have fixed my problem but others might have it.
I think it could be informative to suggest new users who are getting this error, to setup their website on the same vps/server they are using for the bitcoin node.

Thank you very much for your support and your time!

The debug files are full of endless information i have no idea how to approach it.
Regarding the firewall i use ufw.
Here are the settings i have on it:

root@ubuntu:~# sudo ufw status numbered
Status: active

To Action From
— —— —-
[ 1] 443 ALLOW IN Anywhere
[ 2] 8332 ALLOW IN Anywhere
[ 3] 8332/tcp ALLOW IN Anywhere
[ 4] Apache Full ALLOW IN Anywhere
[ 5] 22 ALLOW IN Anywhere
[ 6] 2222 ALLOW IN Anywhere
[ 7] 80 ALLOW IN Anywhere
[ 8] 21/tcp ALLOW IN Anywhere
[ 9] Anywhere ALLOW IN 148.163.126.87
[10] Anywhere ALLOW IN 148.163.126.66
[11] Anywhere ALLOW IN 148.163.126.0/24
[12] Anywhere ALLOW IN 127.0.0.0/8
[13] 443 (v6) ALLOW IN Anywhere (v6)
[14] 8332 (v6) ALLOW IN Anywhere (v6)
[15] 8332/tcp (v6) ALLOW IN Anywhere (v6)
[16] Apache Full (v6) ALLOW IN Anywhere (v6)
[17] 22 (v6) ALLOW IN Anywhere (v6)
[18] 2222 (v6) ALLOW IN Anywhere (v6)
[19] 80 (v6) ALLOW IN Anywhere (v6)
[20] 21/tcp (v6) ALLOW IN Anywhere (v6)

————————————————
Just thought of something.. i use cloudflare, can it be the cause of this?

• This reply was modified 7 years, 3 months ago by patchy.

I have contacted my hosting and they said that they have opened 8332 port for me.
I have also used rpcallowip:
rpcallowip=127.0.0.1/8
rpcallowip=148.163.126.66/24
rpcallowip=148.163.126.87
rpcallowip=148.163.126.72
First 2 i got from the plugin suggestion and the other 2 i got from my host.
Restarted the service and i keep getting this error.

I have created a wordpress website on my vps and used the local ip to setup the plugin and it works there.
I might end up migrating my website to my vps but i prefer to keep it on my current shared hosting since i am afraid there will be bad consequences by me managing my own apache2 wordpress website on a vps (such as installations that i have to make like curl etc..)
So my best shot is to fix this problem..
You said you could see it blocked, can you still see it as blocked? since my hosting provider opened it.

Thank you for your reply.

My wordpress is hosted on a shared hosting platform.
And my vps is on a different hosting.
I didn’t understand what you mean when you said “there is a firewall on your WordPress machine that blocks outgoing connections to non-standard ports”.
Does it mean that my shared hosting on which my wp is installed on is causing the error? since this is a shared hosting and it might block this port?

————————————-
I also tried to open the 8332 on my vps and then tested it using telnet as you said:

root@ubuntu:~# sudo ufw allow 8332/tcp

root@ubuntu:~# iptables -I INPUT -p tcp -m tcp –dport 8332 -j ACCEPT

root@ubuntu:~# telnet 213.32.15.51 8332
Trying 213.32.15.51…
Connected to 213.32.15.51.
Escape character is ‘^]’.
Connection closed by foreign host.
————————————-
Also did this to check the ports on my vps:

root@ubuntu:~# sudo netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8333 0.0.0.0:* LISTEN 1342/bitcoind
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1097/sshd
tcp6 0 0 :::8332 :::* LISTEN 1342/bitcoind
tcp6 0 0 :::8333 :::* LISTEN 1342/bitcoind
tcp6 0 0 :::22 :::* LISTEN 1097/sshd

————————————-

It didn’t fix the error.

• This reply was modified 7 years, 3 months ago by patchy.