Failed to connect after Apple time machine re-install
Posted: January 15th, 2015, 4:19 pm
Dear all,
I would need help with a quite peculiar problem, which came up after I reinstalled my system (iMac 2007).
Here the history:
My Sabnzbd was running well with xsusenet.
Then my hard drive crashed. I have for data rescue a double approach: I have monthly Carbon copy clones on an external Firewire Drive and I have the daily time machine backups.
When the hard drive of my iMac (Mavericks) crashed, I continued working on my iMac booting up via Firewire from the Carbon Copy Clone (old clone). Without problems sabnzbd was connecting fine and still does, if you boot via the external old clone.
After putting a new hard drive in my Mac I reinstalled my last time machine backup (new TM clone). So far so good. Now I wanted to download with sabnzbd on my trusted xsusenet...and the following appears:
https://localhost:9056
[Errno 61] Failed to connect: (60, '[Errno 64] Host is down') -1@reader.xsusenet.com:600
To check if it is a remote issue, I contacted Xsusenet...account is fine.
I booted my external old clone, just to check connectivity....and sbnzbd worked fine and can connect!!!How weird.
I reinstalled then sabnzb on the new TM clone, used version 0.7.17 and 0.7.20 for Mavericks on the newTM clone...nothing.
I deleted the hidden sabnzbd.ini, reinstalled even with the wizard, still the same error code.
Now tis getting even weirder...if I boot my new TM clone normally, but I don't use the there installed sabnzb application, but open sabnzb.app on the external HD (of the old clone installation),ALAS...I can connect and download.
So I thought, no problem, I just copy the sabnzbd.app from my old clone to the new TM clone....not working.
I copied sabnzbd together with the hidden sabnzbd.ini files to the new TM clone...still not working.
I am running out of ideas, what I could do to fix this...
Can anyone help, or did encounter something similar? I can just not wrap my head around this, since the port and host configuration seems to be fine, if I start the .app externally. Are there any ports maybe interfering with each other? I changed host and port configuration BTW on the new TM clone from default to others and back, also no change.
I hope I could explain my dilemma.
Thanks a lot in advance and best regards,
HoschMosch
I would need help with a quite peculiar problem, which came up after I reinstalled my system (iMac 2007).
Here the history:
My Sabnzbd was running well with xsusenet.
Then my hard drive crashed. I have for data rescue a double approach: I have monthly Carbon copy clones on an external Firewire Drive and I have the daily time machine backups.
When the hard drive of my iMac (Mavericks) crashed, I continued working on my iMac booting up via Firewire from the Carbon Copy Clone (old clone). Without problems sabnzbd was connecting fine and still does, if you boot via the external old clone.
After putting a new hard drive in my Mac I reinstalled my last time machine backup (new TM clone). So far so good. Now I wanted to download with sabnzbd on my trusted xsusenet...and the following appears:
https://localhost:9056
[Errno 61] Failed to connect: (60, '[Errno 64] Host is down') -1@reader.xsusenet.com:600
To check if it is a remote issue, I contacted Xsusenet...account is fine.
I booted my external old clone, just to check connectivity....and sbnzbd worked fine and can connect!!!How weird.
I reinstalled then sabnzb on the new TM clone, used version 0.7.17 and 0.7.20 for Mavericks on the newTM clone...nothing.
I deleted the hidden sabnzbd.ini, reinstalled even with the wizard, still the same error code.
Now tis getting even weirder...if I boot my new TM clone normally, but I don't use the there installed sabnzb application, but open sabnzb.app on the external HD (of the old clone installation),ALAS...I can connect and download.
So I thought, no problem, I just copy the sabnzbd.app from my old clone to the new TM clone....not working.
I copied sabnzbd together with the hidden sabnzbd.ini files to the new TM clone...still not working.
I am running out of ideas, what I could do to fix this...
Can anyone help, or did encounter something similar? I can just not wrap my head around this, since the port and host configuration seems to be fine, if I start the .app externally. Are there any ports maybe interfering with each other? I changed host and port configuration BTW on the new TM clone from default to others and back, also no change.
I hope I could explain my dilemma.
Thanks a lot in advance and best regards,
HoschMosch