NodeSquirrel status?

nodesquirrel.com is also off the map, so it's not looking good people…?
Alternatives?

Affecting us as well. For last few days it gives error "The NodeSquirrel server returned the following error: php_network_getaddresses: getaddrinfo failed: Name or service not known".

Looking forward for updates.

I also get same error via Drupal admin panel
The NodeSquirrel server returned the following error: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution

and I cannot access site nodesquirrel.com via browser.

The domain nodesquirrel.com doesn't even expire until 11-26-2019... I've tweeted at both NodeSquirrel and Pantheon, if I hear back, I'll post here.

I already opened a ticket with the Pantheon with the hope of clarifying this. As soon as I get the answers, I'll post them here, too.

The site is now back ... but https access to it is failing.

https://manage.nodesquirrel.com/ is back as well, but the backup itself is still failing.

I heard from Pantheon
"a DNS server went down. They have updated to a new server and everything seems to be working."
Perhaps he's not entirely correct - I'll let him know of this thread.

It appears to be back up. I will report back with any issues.

@myke is it really back?

I tried to run the backup schedule manually with drush. Got this error:

The NodeSquirrel server returned the following error: Error opening socket ssl://api.nodesquirrel.com:443

There is still a problem with HTTPS connection to NodeSquirrel
Perhaps someone could point Ronan or others working on it to
https://www.ssllabs.com/ssltest/analyze.html?d=api.nodesquirrel.com
It fails

It looks like they are serving the https connection from 2 IP addresses
74.121.193.34 and 74.121.199.90
the .34 one does not work - so this could lead to strange results.

This is what I see in Firefox.

An error occurred during a connection to manage.nodesquirrel.com. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

This is utterly ridiculous.

In the backup & migrate module I can see the problem:
The NodeSquirrel server returned the following error: Error opening socket ssl://api.nodesquirrel.com:443

Any idea how to solve it?
Thanks

Any news on this? Been almost 4 weeks now :/

@DamienMcKenna : Thank you!

I can confirm 74.121.199.90 is working while 74.121.193.34 isn't.

Adding the following line to /etc/hosts can be used as a workaround:
74.121.199.90 api.nodesquirrel.com

e5sego, thank you for comment #23. I'm not much of a coder, so can I ask for a bit more explanation? I'm not finding a file /etc/hosts in the node squirrel module. Where should that line be added? Thanks.

If you have shell access, you can also set the nodesquirrel_default_endpoint_urls variable via drush:
drush vset nodesquirrel_default_endpoint_urls, 74.121.199.90/services/xmlrpc
Run this command within the sites/default or your instance directory. Keep in mind to reset this variable after the DNS issue is fixed:
drush vset nodesquirrel_default_endpoint_urls, api.nodesquirrel.com/services/xmlrpc

If you don't have shell access, https://www.drupal.org/sandbox/fabianferns30/2561535 may be you friend.

I've updated vars with new endpoint but still get error: "The NodeSquirrel server returned the following error: Error opening socket ssl://74.121.199.90:443"

To check the vars I used `drush vget nodesquirrel` and realize there are 2 so I've updated both.

nodesquirrel_default_endpoint_urls: 74.121.199.90/services/xmlrpc
nodesquirrel_endpoint_urls: 74.121.199.90/services/xmlrpc

Tried clearing caches/running cron but to no avail. Any ideas?

+1 with this issue
The NodeSquirrel server returned the following error: Error opening socket ssl://api.nodesquirrel.com:443

It seems the site has ssl issues.

For me helped making 2 changes:

drush vset nodesquirrel_endpoint_urls "74.121.199.90/services/xmlrpc"

and solution from here

https://www.drupal.org/project/backup_migrate/issues/2851756#comment-122...

@dreamer777 I can't use drush on my hosting, so how do I make the vset settings? Can I do that directly in the database?

To the backup_migrate support: what is happening with this issue? Is there a fix in the works? Do I need to move on to another backup destination? Please advise and thank you.

I am still being charged by NodeSquirrel.

Boycot Pantheon.

Not according to this.

https://modulesunraveled.com/podcast/136-details-nodesquirrel-acquisitio...

Thats just great. How about you find out from Ronan who owns it now and have them answer for their defective product.

Thank you.

@DamienMcKenna To add some small perspective to the current stalemate, Ronan Dowling, as you know, is also the creator of Backup and Migrate. Shortly after Drupal 8's release in 2015, I began contacting Ronan about his plans to port the D7 version to D8. He responded multiple times affirmatively that he indeed had plans to work on it, as he has to you recently regarding NodeSquirrel. However, no work took place for many months which he later said was due to health problems and job commitments. I believe he honestly has the best of intentions for both modules, but he eventually handed over maintenance of Backup and Migrate to others who could take it forward, and no work has been done on NodeSquirrel to my knowledge since 2015. I'm not even sure if Ronan is still employed by Pantheon.

Quite a few Drupal users have posted within the Backup and Migrate issues queue for at least a year now that they have been seeking alternatives to NodeSquirrel, so that may be more of a serious option now than ever before unless a new maintainer wants to voluntarily take over NodeSquirrel which is an open-source module here at Drupal.org. I think it's a good idea to disable the built-in NodeSquirrel support for the D7 version of Backup and Migrate, as you have done, until it becomes clear what the future of NodeSquirrel will be.

OK, I just discovered that nodesquirrel is working this morning.
Configured backup was successful (nothing patched)
Was able to login to NS to see the backup.

backup_migrate: 7.x-3.6

Anyone else having success?

I contacted Pantheon with this problem as I was getting no response from Nodesquirrel's support form, and their email bounced. I was met with a "don't care" attitude and they basically said it's not their problem!

Initial reply from them...
"I'm sorry, but there's nothing we can do about this on our side. Nodesquirrel is a separate service with no formal relation to Pantheon. We have backup features of the Pantheon platform we fully support, but debugging issues for an external service is very much beyond our scope."

When I pointed out that on Gorton Studios who started Nodesquirrel say on their site…
https://www.gortonstudios.com/who-we-are, "Gorton Studios was founded in 2001 and actively took new clients through 2015, at which point NodeSquirrel, our backup product, was acquired by Pantheon."

I got this reply...
"Sorry, I wasn't aware of this as I joined Pantheon recently. Still, me and my team are not able to help out here."

Nice, real nice.

The relevant dates:

"When Will NodeSquirrel Go Away?
NodeSquirrel will stop accepting backups after September 30, 2019.

How Long Will Backups be Stored?
Users will be able to download backups through November 1, 2019."

Source: https://pantheon.io/nodesquirrel-service-end-life

Module's page needs to be updated to remove Nodesquirrel.

For Your Information: Backup and Migrate Dropbox now has a fully working and official (covered by the security advisory policy) release which can serve as a full replacement for NodeSquirrel cloud backup (DropBox offers free accounts with 5GB of storage capacity).

Thanks @fietserwin! Just installed and configured the Dropbox module and it works great.