Hello,
Since a few weeks I have problem with clublog automatic upload. The password is 100% correct. I'm able to login to clublog. The log shows
The remote server returned an error: (403) Forbidden.
2016-08-11 22:18:06.8022 ERROR: *** ClubLogManagement: Upload to ClubLog caught in error ******* [Function: #=qhvu6E7Cs4wxbiMK2tHssGX3NEevNsGpmxuIV1bfNXxU=] System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at LogOM.BL.ClubLogManagement.#=q_k8HZb5eJpeZezRkls$3fA==(QSO #=qP$7pLRoHicnRINJyMwHv1g==, String #=qF65LebJ$M5aqnVc9O6EsvQ==, String #=qMRk$XTwkBsIacNP_dP9i2A==, String #=qv3J88_8oyUQZ6zQaMGUrPw==, String #=q90aE2Pl90U92_ZlMz6GbCw==, String #=qCfg$8FK9FyGxetP5zVMB5g==)
at LogOM.BL.ClubLogManagement.#=qhvu6E7Cs4wxbiMK2tHssGX3NEevNsGpmxuIV1bfNXxU=(Object #=qf7c94Bi5HkrQiev0RrLlPg==, DoWorkEventArgs #=q9afmgKRjUD5h72iqAQ$Teg==)
2016-08-11 22:18:06.9945 INFO: Log4OMMainWindow: QSO Add completed:
2016-08-11 22:18:07.0015 ERROR: *** ClubLogManagement: upload caught in error with code:
Thanks
Mario
KC8P
ClubLog upload - (403) Forbidden
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: ClubLog upload - (403) Forbidden
This was a protocol error related to HTTP 1.1
An "internet protocol" error, not something on our Log4OM software side, but on the Clublog server config
The Clublog server is now back to normal opperation
An "internet protocol" error, not something on our Log4OM software side, but on the Clublog server config
The Clublog server is now back to normal opperation
73 Terry G4POP
Re: ClubLog upload - (403) Forbidden
As of today, I don't see a difference:
2016-08-19 21:58:45.2252 ERROR: *** ClubLogManagement: Upload to ClubLog caught in error ******* [Function: #=qhvu6E7Cs4wxbiMK2tHssGX3NEevNsGpmxuIV1bfNXxU=] System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at LogOM.BL.ClubLogManagement.#=q_k8HZb5eJpeZezRkls$3fA==(QSO #=qP$7pLRoHicnRINJyMwHv1g==, String #=qF65LebJ$M5aqnVc9O6EsvQ==, String #=qMRk$XTwkBsIacNP_dP9i2A==, String #=qv3J88_8oyUQZ6zQaMGUrPw==, String #=q90aE2Pl90U92_ZlMz6GbCw==, String #=qCfg$8FK9FyGxetP5zVMB5g==)
at LogOM.BL.ClubLogManagement.#=qhvu6E7Cs4wxbiMK2tHssGX3NEevNsGpmxuIV1bfNXxU=(Object #=qf7c94Bi5HkrQiev0RrLlPg==, DoWorkEventArgs #=q9afmgKRjUD5h72iqAQ$Teg==)
2016-08-19 21:58:45.2297 ERROR: *** ClubLogManagement: upload caught in error with code:
2016-08-19 21:58:45.2252 ERROR: *** ClubLogManagement: Upload to ClubLog caught in error ******* [Function: #=qhvu6E7Cs4wxbiMK2tHssGX3NEevNsGpmxuIV1bfNXxU=] System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at LogOM.BL.ClubLogManagement.#=q_k8HZb5eJpeZezRkls$3fA==(QSO #=qP$7pLRoHicnRINJyMwHv1g==, String #=qF65LebJ$M5aqnVc9O6EsvQ==, String #=qMRk$XTwkBsIacNP_dP9i2A==, String #=qv3J88_8oyUQZ6zQaMGUrPw==, String #=q90aE2Pl90U92_ZlMz6GbCw==, String #=qCfg$8FK9FyGxetP5zVMB5g==)
at LogOM.BL.ClubLogManagement.#=qhvu6E7Cs4wxbiMK2tHssGX3NEevNsGpmxuIV1bfNXxU=(Object #=qf7c94Bi5HkrQiev0RrLlPg==, DoWorkEventArgs #=q9afmgKRjUD5h72iqAQ$Teg==)
2016-08-19 21:58:45.2297 ERROR: *** ClubLogManagement: upload caught in error with code:
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: ClubLog upload - (403) Forbidden
Please turn on debug trace mode in Log4OM help
Try another upload
Then email the logfile to me
DO NOT POST THE LOGFILE ON THE FORUM
Try another upload
Then email the logfile to me
DO NOT POST THE LOGFILE ON THE FORUM
73 Terry G4POP
Re: ClubLog upload - (403) Forbidden
Terry,
Email has been sent.
Thanks!
Email has been sent.
Thanks!
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: ClubLog upload - (403) Forbidden
KC8P wrote:Terry,
Email has been sent.
Thanks!
I require the complete trace file by direct email to my email address as on QRZ/HamQTH not an extract of the file included in the body of a forum email
73 Terry G4POP
Re: ClubLog upload - (403) Forbidden
Done. Sent the original log in .txt
- G4POP
- Log4OM Alpha Team
- Posts: 10817
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: ClubLog upload - (403) Forbidden
This issue turned out to be the use of special characters in the password, like $%#@, once changed back to just alphanumeric everything works.
So I request that everyone avoids using special characters in passwords until we can resolve this with Clublog.
So I request that everyone avoids using special characters in passwords until we can resolve this with Clublog.
73 Terry G4POP