Log4OM

I believe Club Log has changed something in the past few days. Log4OM no longer uploads real-time QSO's to Club Log. The following error is found in the Log4OM_log_20180305.txt file.

2018-03-05 21:19:30.2792 ERROR: *** ClubLogManagement: Upload to ClubLog caught in error ******* [Function: #=qEGluUhJaJhH_wEA$jMy8aP4MJSUqu3ZjXIK63TDKrPA=] System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at LogOM.BL.ClubLogManagement.#=qrBR9Rn4SWCzcEFtu4PErnw==(QSO #=q$zH_oDUl7Iy5IUBJdIL_pg==, String #=qrvEe$H_W8S0ORFaNRSLIPA==, String #=qARV9jBhTGCAr4HqlR6g_qA==, String #=qrs12vVCE1SrCZO$dSJ8j8Q==, String #=qxyv5Udgl3qIJvPDIjzZbAA==, String #=qLJPdVLgt7XhPkP4Oo2s8dg==)
at LogOM.BL.ClubLogManagement.#=qEGluUhJaJhH_wEA$jMy8aP4MJSUqu3ZjXIK63TDKrPA=(Object #=qFxJ5HR20VLXy57qD4bmGwg==, DoWorkEventArgs #=qt5qpURcNef6t_W7$_rhw2w==)
2018-03-05 21:19:30.2802 ERROR: *** ClubLogManagement: upload caught in error with code:
2018-03-05 21:19:53.6137 INFO: HRDLogManagement: ON AIR start

Thank you for any help with this.
73 de Tim, KQ8M

Tim,
It says it has timed out so I would suspect that your internet or Clublog was at fault

I have just checked ant the upload is working fine

Exactly the same with me. Just noticed automatic upload stopped 3 days ago to Clublog. Nothing changed, internet connection (timeout unlikely occured), user datas, checked everything. Tried to force upload one qso by right click on it but did not make it.

Log file sais this from that action:

2018-03-06 09:15:50.0645 ERROR: *** ClubLogManagement: Upload to ClubLog caught in error ******* [Function: #=qEGluUhJaJhH_wEA$jMy8aP4MJSUqu3ZjXIK63TDKrPA=] System.Net.WebException: Időtúllépés történt a művelet végrehajtása során
a következő helyen: System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
a következő helyen: System.Net.HttpWebRequest.GetRequestStream()
a következő helyen: LogOM.BL.ClubLogManagement.#=qrBR9Rn4SWCzcEFtu4PErnw==(QSO #=q$zH_oDUl7Iy5IUBJdIL_pg==, String #=qrvEe$H_W8S0ORFaNRSLIPA==, String #=qARV9jBhTGCAr4HqlR6g_qA==, String #=qrs12vVCE1SrCZO$dSJ8j8Q==, String #=qxyv5Udgl3qIJvPDIjzZbAA==, String #=qLJPdVLgt7XhPkP4Oo2s8dg==)
a következő helyen: LogOM.BL.ClubLogManagement.#=qEGluUhJaJhH_wEA$jMy8aP4MJSUqu3ZjXIK63TDKrPA=(Object #=qFxJ5HR20VLXy57qD4bmGwg==, DoWorkEventArgs #=qt5qpURcNef6t_W7$_rhw2w==)
2018-03-06 09:15:50.0756 ERROR: *** ClubLogManagement: upload caught in error with code:
2018-03-06 09:20:31.4340 INFO: SharedFunctionsManagement: INTERNET CONNECTION ACTIVE
2018-03-06 09:25:31.4340 INFO: SharedFunctionsManagement: INTERNET CONNECTION ACTIVE
2018-03-06 09:30:31.4361 INFO: SharedFunctionsManagement: INTERNET CONNECTION ACTIVE

Help would be appreciated.



George

Checking if they changed something... it seems a frequent behaviour lately

Hi Lele,

there was a problem in the last few day´s here too but this morning it´s back and it looks like that
uploads to CL are working. Using the "latest" RC2

(1.32.0).

There are a series of posts on hamlogger for the logger32 group. They experienced the same problem. Turns out Club Log has IPV6 in there DNS setup and aren't using V6 or isn't setup correctly on their end. Unchecking V6 on my adapter settings fixed the problem. Now working. Club Log is looking into the problem.

Thank you for your time.
73 de Tim, KQ8M

This is now fixed on Club Logs end.

Hi all

If you've had problems connecting to Club Log over an IPV6 network in the last few days, please be advised there was a routing issue (which has been resolved) so this should not be causing any further trouble.

Many thanks to Stu, AC6AG for helping out!

vy 73
Michael G7VJR

73 de Tim, KQ8M

Upload to Clublog still not working for me,

2018-03-13 22:51:13.9246 ERROR: *** ClubLogManagement: Upload to ClubLog caught in error ******* [Function: #=qh_25wavTIgroNnlrc7baef5lmv8PTwTm0i0K$DJ6oXQ=] System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at LogOM.BL.ClubLogManagement.#=q0v3tEp$Po9wPLTRMNioJJw==(QSO #=qsTxi0MxDtNnhjHIxUSvfPA==, String #=qzraIP2mdZ5O5gTekx4wkVw==, String #=qFREdhbz9AbmajcRT_4I69g==, String #=qGjBuSb965oyB8RHqKFJk$w==, String #=q8ExVkGtsmpmWrJSfBYxA1w==, String #=qMg9SbEZ7dKwwr_bU3y7tSw==)
at LogOM.BL.ClubLogManagement.#=qh_25wavTIgroNnlrc7baef5lmv8PTwTm0i0K$DJ6oXQ=(Object #=qt9U6pL_Xy4JtUAQpTAB4LQ==, DoWorkEventArgs #=qSWlKfS1Jb1FFi1R3XayAlQ==)
2018-03-13 22:51:13.9251 ERROR: *** ClubLogManagement: upload caught in error with code:

Clublog recently changed their addresses for those services.
Forbidden may be:

- The URL is no more active for upload, but this will affect everyone
- Your entered USER/PASSWORD is incorrect.

I think it's the second one. We're working on a new version to be compliant with unexpected changes by IOTA and CLUBLOG

I had to change my password when Clublog moved over to IPV6 or whatever they did,

But I have updated Log4OM with the new password but it still fails to send my QSO's to CL ???