Hello, first let me be straight, with this method I and my fellow AT member have fixed annoying server timeout thingy forever, but it still may not help you, so only thing how to see it is testing it.
We noticed that this timeout thing started to appear once AT admins added 3 new devices so that being said at some point data that server needs to send you back became heavier. Next itself is in BETA mode and is not stable, as well there are a lot of KG's ( kilograms ) to send you back when your machine makes a request.
Remember that a request from a device has to pass through multiple checkpoints on its way to the server. Any of these checkpoints can be busy and overtaxed with requests from other computers and devices on the network for other servers. So on TOP of that, if AT server is overloaded with requests from other users + network checkpoints are busy, it may take more time to load ( send you back the requested info ).
A lot of other factors such as how powerful your PC is, how powerful is your internet speed, your location, how big project you are running, etc etc.
Here is a video example of a timed out server, where you still can work ( so it is not AT side ):
https://drive.google.com/file/d/1lunsomsLwFTBFwhwJ8y8yQtIwzWZB6wv/view?usp=sharing
AT admins don't run in such error ( As Andre stated they are not able to reproduce it ) because I believe, they have powerful machines, powerful net speed, and the server is located in the basement ( lol joke ) It's just really close to them.
NEXT being " heavy " itself with all those features and tools, unstable, server loaded with requests ( busy ) etc, etc, can lead to the annoying msg we use to get lately.
Because:
By default settings, your machine/browser can think that the server you are trying to connect is not responding and gives up on waiting - server timed out, while in reality, it is not, but server responds to your request longer.
Here is the video with registry edit info with steps to be done:
https://drive.google.com/file/d/16ox0M4W4tGpz9kgOgZZr2rMtAUWls_5V/view?usp=sharing
After this thing, I have yet to receive an error once, before that I received it every 15 minutes or so at random moments + when I deleted the added file in regedit folders, Timeout thing bugged me again.
Hope this helps, I have no idea for others.
Comments (5)
how would i do this on a mac?
I think I've found a better fix: Just bypass your AT Next cache. On Windows/Linux, it's "Ctrl+F5" and on Mac it's "⌘Cmd+⇧Shift+R"
I tried it before didn't work for me though. But is worth trying because cache really can mess things up sometimes. Proven.
I think that I found another solution that might help other people. I think that the problem is occurring when Next is trying to sign you in from a facebook/google/soundcloud account. if you enter https://next.audiotool.com/ without signing in from incognito, next asks you to sign in from the main page. if you try to sign in with a google account, chrome will stop you from connecting because it thinks that the script is unsafe. go up into your address bar, and click on the box with a red x to show a popup and click the link that says "load scripts". the page will refresh and you should be able to log into audiotool and start next from there.
worked for like 20 minutes, timed out and now I cant start it. oh well