xmr connection errors

An existing connection was forcibly closed by the remote host.

I am getting "connection reset by peer" on my proxy as well.  reset everything - no help. 

It has something to do with the German IP address I think.  I changed my IP to the USA server and it is working.  I "was" connected to the German IP at 138...... 

https://dnschecker.org/#A/xmr.coinfoundry.org

You are very right, this solved it for me too. Thanks!

same here. since yesterday couldn't connect to the xmd.coinfoundry pool, any port. 

manually changing to the 97. ... ip works. 

is there any benefit from using the european ip (when located in europe)?

Cheers

location: EU

No, didn't use ssl/tls, as this never worked for me (any port +100, tls=true). 

Didn't try for the other (non-eu) ip yet. 

I just now tried it out, still not working. Here is the output, maybe it helps (using xrm-stak):

using ip 97... no ssl/tls: works

using ip 97... with ssl/tls:

05-23 16:32:48] : Fast-connecting to 97.107.139.34:3134 pool ...
[2018-05-23 16:32:48] : SOCKET ERROR - [97.107.139.34:3134] 139946438420224:error:02002071:system library:connect:No route to host:../crypto/bio/b_sock2.c:108:
139946438420224:error:2008A067:BIO routines:BIO_connect:connect error:../crypto/bio/b_sock2.c:109:
139946438420224:error:02002071:system library:connect:No route to host:../crypto/bio/bss_conn.c:169:hostname=97.107.139.34 service=3134
139946438420224:error:20073067:BIO routines:conn_state:connect error:../crypto/bio/bss_conn.c:173:

using xmr.coinfoundry.org not ssl/tls:

[2018-05-23 16:26:22] : Fast-connecting to xmr.coinfoundry.org:3034 pool ...
[2018-05-23 16:26:59] : All pools are dead. Idling...
[2018-05-23 16:26:59] : SOCKET ERROR - [xmr.coinfoundry.org:3034] CALL error: Timeout while waiting for a reply
[2018-05-23 16:27:29] : Fast-connecting to xmr.coinfoundry.org:3034 pool ...
[2018-05-23 16:27:29] : Pool xmr.coinfoundry.org:3034 connected. Logging in...
[2018-05-23 16:27:39] : SOCKET ERROR - [xmr.coinfoundry.org:3034] CALL error: Timeout while waiting for a reply

using xmr.coinfoundry.org with ssl/tls:

[2018-05-23 16:31:25] : Fast-connecting to xmr.coinfoundry.org:3134 pool ...
[2018-05-23 16:31:25] : SOCKET ERROR - [xmr.coinfoundry.org:3134] 139878067070720:error:02002071:system library:connect:No route to host:../crypto/bio/b_sock2.c:108:
139878067070720:error:2008A067:BIO routines:BIO_connect:connect error:../crypto/bio/b_sock2.c:109:
139878067070720:error:02002071:system library:connect:No route to host:../crypto/bio/bss_conn.c:169:hostname=xmr.coinfoundry.org service=3134
139878067070720:error:20073067:BIO routines:conn_state:connect error:../crypto/bio/bss_conn.c:173

Cheers

Guys, could we try to pin this down to a server location? Could everyone edit their post to include their geographical location? EU, US or Asia/Pacific/Oceania?

xmr.coinfoundry.org seems to be working again.

Have tried several vpn locations - all fine.

Didnt use ssl/tls though.

xmr.coinfoundry.org is now working for an hour.

There is a new - occasionally - error:

"no active pools - stop mining"

Not to be rude, but what does this "under review" tag mean? Is something happening anyway?

For me, everything is being normal again with the xmr.coinfoundry.org adress.

Is everyone using SSL/TLS?

I've tried both with and without TLS. Happens on both but probably more so on TLS. Happening frequently on the EU IP address again.

I am not using SSL.  I am located in the USA but had the German IP specified on my proxy because I had so many issues with the USA IP at one time.  

I've checked the logs of my server and found a possible explanation.

On the very day I expirienced those errors my server had obviously a restart.

Since my server and the EU (german) ip of coinfoundry belong to the same hoster it might explain the trouble.

The hoster must have issues in his data center and/or network.