I recently upgraded from version 3.4.1 to version 4.6.16. The program initially would open but now it will not. I’m getting an error message "error: backend/unavailable and “failed to connect to RoasTime’s backend after retrying 5 times”. I’ve tried deleting and redownloading the software but I get the same message after each attempt to open the downloaded file. Any ideas on how to get this to work? Thanks.
can you please check if you firewall is set to block any parts of roastime?
Jacob:
I think that i will clear my hard drive, reload Windows and try loading Roastime again. I didn’t have the computer hooked up to the bullet when i first opened Roastime; maybe that was the original sin. However, until then if you have any ideas let me know. Thanks.
Jim C.
FYI; I fixed it by reinstalling Windows and repeating the download/startup procedure. Looks good to go now.
FWIW - re-installing your OS is a pretty drastic measure and this was probably more likely related to firewall settings. Glad you got it sorted regardless!
My laptop is used primarily for running Roastime and there is little else on the computer. It took maybe 30 minutes to reinstall Windows. I spent way more time trying to adjust the firewall; when I shut down the firewall and Roastime still gave me the same error message I decided on the drastic.
2 Likes
@mcaillio I’m experiencing the same error code (“backend/unavailable”) - I’ve turned my firewall off completely to troubleshoot, but am still getting the error. Any other solution ideas? As you said, re-installing the OS is pretty drastic and I would rather avoid doing so
What OS are you on? I would try deleting the app data. In the past, backend/unavailable is due to corrupted data in most cases.
I’ve got this same message showing for me now. MacOS. Have deleted and redownloaded the app, opened the firewall, same result. Any advice?
Can you try deleting these directories?
Library>Application Support> roast-time
Library>Application Support> RoasTime
I’m having this issue now after updating this morning. I am running 4.6.26 and keep getting the failure to connect and backend unavailable. I deleted those directories, restarted my machine and even updated my MacOS Software to the latest version all to no avail. I really need to roast today so I guess I’m going all manual control and hoping I remember my recipes.
What is the issue with this connection failure?
Hey @thewildcup
I accidentally fat fingered a release to beta today that was broken. I reverted it within ~10 minutes, but you may have gotten that faulty update. Do you have a 3rd directory named roastime? On Linux I have roast-time, RoasTime, and roastime. The one you want to delete is the one with the deps directory nested inside it.
1 Like
All good. I don’t have a 3rd directory by that name. I do have a folder called “deps” under Library>Application Support>RoasTime>Deps with a bunch of stuff in it but not sure what I would look for to delete.
You would just delete the whole folder. That would make RT start with the dependencies released with the main release and update again once open.
So I deleted the folders and am now able to successfully log in. Thanks!
how do I delete the folders on mac? sorry if this has been explained
You can open terminal and copy/paste these commands:
rm -rf ~/Library/Application\ Support/roast-time
rm -rf ~/Library/Application\ Support/RoasTime
Version 4.6.21 Backend Error
Application not allowed to access network.
12 minutes ago
Feature:
Firewall
The application roastime-backend-win-x64.exe attempted to connect to the Internet: File path: C:\Users\User\AppData\Roaming\RoasTime\deps\roastime-backend-win-x64.exe Destination: 208.67.222.222/0 Protocol: UDP Port: DNS NETGEAR Armor Firewall detected malicious activity and denied access for this application. If you want to grant access, click on the button below or go to Firewall - Rules.
Honestly, not sure how we can silence this warning without buying a more expensive certificate. We do send and receive profiles and other data up to our servers. I think this is a pretty common issue when opening any 3rd party application that sends data out.
Will keep looking into it, but if anyone has advice - happy to hear it!