I can’t upload my latest SOTA activation.
I’ve tried it with Firefox, Chrome, and Firefox’s private mode. Always the same problem in the last step.
The ADIF file looks okay to me.
Does anyone have any idea what the cause might be?
73, Mathias
DH1WM
Make sure you don’t have any privacy blockers running that block the transfer between the domains used.
I’m trying to upload an ADIF for an activation. When I hit submit it just sits there rotating. I am using Chrome on Windows and don’t think I have a privacy blocker set. As I write this it has just given me
PS. I do have an Ad Blocker but it’s turned off for the database page.
Recent Chrome update?
Something is blocking the transfer between different domains used. (Off the top of my head, sotadata.org.uk > api-db2.sota.org.uk) Some security updates think this bad. I don’t use Chrome so I don’t know what the fix is for that browser.
It works for me with Brave (Chrome without Google’s spyware) and Firefox. I’m not telling you to change! There will be something that unblocks this on Chrome but I don’t know what it is.
The upload has actually worked now without me changing anything in the browser. I have another upload to do so I’ll see if that works better.
The second upload is doing the same thing - just sitting there and rotating. And it’s just given me the error “Timed out in bb8”.
There looks like the second API server had a temporary glitch but has reconnected and sorted itself out.
Started about 09:35 and ended around 09:58 UTC. Only an issue on one of the servers in the load balance, hence it occasionally working for you
I tried uploading again but it still rotated. Then it said I had a previous upload, would I like to restore it. I ended up deleting it. If I go to my stats page it doesn’t show my recent activations - it looks like its still holding a database lock.
I’ve come back to this after an hour and it has all worked now. I guess the database lock times out after a while.
I just tried to upload the logs from my vacation last week. The first few uploads were more or less smooth. Now I had the problem, that only my S2S get uploaded as chases, but not the activation itself. I think I will try again later or tomorrow. Best 73s 
The problem Thomas is when we have a problem like earlier and people report an issue, many users will go and try to see if there is an issue or if it is fixed. This can make the problem worse. Similarly when we post a problem has been fixed, many people go and test the system again pushing up the load.
Checking myself I noticed there were some things not right. This resulted in lots of failed requests and queued jobs. All in all things were not happy. After a lot of digging and looking at what was happening I performed a deeply technical fix on the task running on api server #2 and things look like they are OK.
At this point can I remind you of a line Tom Hanks says in the film Apollo 13. Hanks is playing Cmdr. Jim Lovell and the crew have just fabricated a Heath Robinson adapter to fix a square Lithium Dioxide container into a round hole to filter out Carbon Dioxide. Hanks’ character notices the other 2 crew are breathing very shallowly and he says “Just breathe normally guys…” and everything works.
So I would say, the DB etc. should be working fine, but just use it normally. Upload logs etc. but don’t all rush to test it to see if it is fixed. M’kay? And for your info, I’m watching what is happening so I’ll be able to see who didn’t do as asked. 
This, of course, stands half a chance of being avoided if folk don’t report the problem on this reflector, but use the Contact SOTA form instead. The link’s in the top menu on this reflector and on the main SOTA site, and in the “SOTA Links” menu on SOTA Watch…
The only obvious downside is that there’s no easy way to see whether the problem you’re having has already been reported, 
I have to Fess up. I’ve been having issues for months. Thought it was a mixture of fat fingers and my phone. Sometimes it makes two or three attempts to get an adif to upload. Sometimes it goes first try.
I was saved a few times in the past by the ‘restore’ function during manual entry but it doesn’t seem to work for me anymore. 
I tried an ADIF upload after taking a log file from Mini-FT8, SOTADATA didn’t like it.
I’m just a pencil weilding Luddite being forced to use modern devices. 
The last few activations worked for me.
But today I’m having the same problem again.
I can understand your fear, but the issue is with uploading an ADIF log. Either some people have a log to upload or they don’t. The rest of the database seems to work fine.
What I can say is that for me, the upload still doesn’t work. I was able to upload a chaser ADIF just now without problems. But I am not able to upload the rest of the activations that I made last week.
I don’t want to stress! I can also upload the remaining logs in a week. I just wanted to let you know, that there might be a problem with the database.
Best 73
Thomas
Send me the ADIF to andy.gm4lld AT gmail.com
There is an issue. I cleared all the stuck process earlier today. Then I came back this evening and it was broken so I cleared them and it is broken again.
In fact there seems to be a problem with the ADIF from this one day. I just tried another day and it worked flawlessly. This is strange, as I directly uploaded the export file from the PoLo app in both cases. I will investigate this further.
Thank you for assisting. I might send the log to you later if I can’t find the problem by myself!
I think I can now exactly tell you, where the bug happens!
Sometimes when I get a GMA reference, I log it under the SOTA reference on the fly. When I clicked the “Verify Log” button, I got the expected error message, that the S2S reference is invalid. As usual, I deleted this S2S reference. Clicking on “Verify Log” again worked and I was able to submit the QSO.
But it seems like the online editor has a bug such that I got the error “[object Object]”. I confirmed this with two ADIF test files each containing just a single QSO. There is only on difference beween these two files:
In fact I was able to upload file B flawlessly, but file A lead to exactly the same “[object Object]” error.
Can you please check, that clearing a S2S reference in the online editor works correctly?
Best 73
Thomas
Send us the failing log via PM on here.
