Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
updated for MSSQL11
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
Our site using mssql11 is down even after putting in the IP in our web.config file. In this thread you are saying to use 173.0.136.201,5211 but in chat they are saying to use 173.0.129.40. Which is it?
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
173.0.129.40 is the IP to use for sites to connect to the server.
for external management access, it is 173.0.136.201,5211
I’ve confirmed multiple times now that the 173.0.129.40 is working as I’ve set some clients to work with it already.
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
Just an update that chat has told us to use 173.0.129.40, but after updating our web.config file, we are getting the same error still. I have submitted ticket HJR-72007-641.
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
We’ve brought the old IP back up now, it was getting a brutal attack that was forwarding that traffic on to the new and using a lot of traffic on both sides to we’d taken it down. (MSSQL11) this was only a temp measure, but so is the ip redirect.
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
explained, replied, short term fix done, and long term fix in your hands now 
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
Just wondering if the backup/restore script is available for MSSQL13 (cluster 1)?
I’ve tried mssql13.jodo_shared.com/mssql/backup.aspx and restore.aspx but they’re not there.
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
did not, but does now… also can use it on http://173.0.129.90/mssql or your own service domain.
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
I think there’s a typo in the OP.
You’ve written “MSSQL13 173.0.135.201,5213”
But it’s actually 173.0.136.201,5213
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
yes yes it is 136. that si why people have been getting it wrong, I typo’d!
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
Been a mysterious surge in support emails, huh?
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
Just tried mssql2.jodoshared.com/mssql/Backup.aspx
Got an asp.net error. Any chance of a quick fix?
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
there is still someone on mssql2?
It is giving an encryption error, going to take a while to track that one down, I’ll check it after win25 completed.
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
I’m tired of moving servers. All that packing, having to make new friends…
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
Hi Stephen,
Same request for mssql3, mssql9 and mssql10. Especially 9 and 3 would be great to have backup possibility asap…
Thanks and best regards!
Jan-Pieter
Re: MSSQL servers - no longer open to outside on new and old will be set this way soo
ports just go in order, I am working on backups starting monday
Hello,
Below are the ip addresses and port for the respective server for external management access :-
========================================================================
CL1 - Cluster-1
CL-2 - Cluster-2
- MSSQL Servers
Server IP Address Port
CL1- MSSQL1 173.0.136.201,5201
CL1- MSSQL2 173.0.136.201,5202
CL1- MSSQL3 173.0.136.201,5203
CL1- MSSQL4 173.0.136.201,5204
CL1- MSSQL5 173.0.136.201,5205
CL1- MSSQL6 173.0.136.201,5206
CL1- MSSQL7 173.0.136.201,5207
CL1- MSSQL8 173.0.136.201,5208
CL1- MSSQL9 173.0.136.201,5209
CL1- MSSQL10 173.0.136.201,5210
CL1- MSSQL11 173.0.136.201,5211
CL1- MSSQL12 173.0.136.201,5212
CL1- MSSQL13 173.0.136.201,5213
CL2- MSSQL1 173.0.136.201,5001
CL2- MSSQL2 173.0.136.201,5002
CL2- MSSQL3 173.0.136.201,5003
CL2- MSSQL4 173.0.136.201,5004
CL2- MSSQL5 173.0.136.201,5006
CL2- MSSQLSD 173.0.136.201,5111
VZSQL1 173.0.136.201 5101
OLD CL2-SDMSSQL 173.0.136.201 5401
HVSQL1 173.0.136.201 5402
- MYSQL Servers
Server IP Address Port
CL1-MYSQL1 173.0.136.201 6117
CL1-MYSQL2 173.0.136.201 6118
CL1-MYSQL3 173.0.136.201 6119
CL1-MYSQL4 173.0.136.201 6120
CL1-MYSQL5 173.0.136.201 6121
CL1-MYSQL6 173.0.136.201 6122
CL1-MYSQL7 173.0.136.201 6123
CL1-MYSQL8 173.0.136.201 6124
CL1-MYSQL9 173.0.136.201 6125
CL1-MYSQL10 173.0.136.201 6126
CL2-MYSQL1 173.0.136.201 6001
CL2-MYSQL2 173.0.136.201 6002
CL2-MYSQL3 173.0.136.201 6003
CL2-MYSQL4 173.0.136.201 6004
- PGSQL Servers
Server IP Address Port
CL1-PGSQL1 173.0.136.201 7026
CL1-PGSQL2 173.0.136.201 7027
CL1-PGSQL3 173.0.136.201 7028
CL1-PGSQL4 173.0.136.201 7029
CL2-PGSQL1 173.0.136.201 7101
- PLESK Servers
Server IP Address Port
Plesk-MSSQL1 173.0.136.201 10001
Plesk-MYSQL1 173.0.136.201 20001
db backup? you mean i’ve been filing tickets to get jodo to backup my db’s needlessly?
why didn’t they say something about it?
where are dbBackup details plz
Except that was said back in 2011. There used to be a web page on each of the SQL servers, where one could download a live backup, or upload one to be restored. It was AWESOME to say the least. I think Stephen set it up himself.
I’d love that to come back, but I think it was discontinued for security reasons. Stephen, any possibility of providing those again?
1 Like
The software was custom yes, and some .net security changes and Windows 2008 made it break 
I don’t have a working workaround for the issue at this time either, it would also vary by server likely as we have now a couple 2000 left, 2005, 2008 and 2012 SQL Servers, 2012 actually took quite some work to get going as they have changed a lot in the stored procs on it to manage DBs.
I’ve had an idea for a long time on an ‘easy’ way to get a working backup system going, but it wouldn’t ever be able to do the restore like the old system. I attempted it on one server and it didn’t succeed and haven’t given another shot. What’s interesting to me here is that a similar routine to the one we used that broke was used on WebSitePanel, and their SQL download backup routine is also broken since that time for remote SQL Servers like we run.
I guess the remote aspect to it is a blessing and a curse at times, if it was local it could just copy to the web account folder and be available, but it would also be inherently less secure. I am rambling and tired, needing to go to sleep, but I’ll look into it again as I have time now.
2 Likes