Clublog upload workaround

11 posts / 0 new
Last post
KL2ZZ
Clublog upload workaround

I can't reply to the clublog upload thread, so I apologize for the duplicate.

Bandaid fix

If you're uncomfortable with building CQRLOG from source, append this to your /etc/hosts file as a workaround. aliasing secure.clublog.org to clublog.org works for me and should work for you as well until new packages get built:

5.153.81.176 secure.clublog.org clublog.org

NOTE: I *do not know* if clublog has a dynamic IP that may change over time. This IP is correct as of the time of writing though. (31 Dec 2022)

73,

James
KL2ZZ

oh1kh
Clublog upload workaround

Hi James!
Thanks for sharing that quick fix!
It should be easier and quicker to do than compile the source.

For further help I think that those hard coded addresses should be moved to preferences with some timetable.
This is the problem with computer world. Things do not last for long time. Continue updating is needed to keep things running.
If the address does not change the API procedure changes and we just have handle those.

--
Saku
OH1KH

py2ad
Dont works for me.

Dont works for me.
Shows me that upload was OK, but doesnt appears on Clublog

I am using 2.6.0 (105) on Ubuntu

Rey
PY2AD & PY5AD

dl7vea
Does not work for me either.

Does not work for me either. With debuging enabled I receive a "301 Permanently moved" error from the clublog side.

F5JQF
Does not work for me either.

Hello,
Dont works for me. I modified the Host file as needed.
5.153.81.176 secure.clublog.org clublog.org
With each new entry in the direction of ClubLog, nothing appears. I work around the problem by manually updating ClubLog.

Thanks for reading me.
73' Yves F5JQF

CqrLog ver 2.6.0 (001) Gtk2 / Linux Mint 20.3 Cinamon

Yves, F5JQF
CQRlog Ver.2.6.0_(124)_GtK2 / Hamlib 4.5.5 / Linux Mint 21.3 Cinnamon
..

oh1kh
Does not work for me either.

HI Yves!
At the moment (Mon 2023-01-30 08:02UTC) by "who.is" web tool page it seems that secure.clublog.org has a valid dns record but it point to different IP address than 5.153.81.176

secure.clublog.org exists and you can ping it.
[saku@hamtpad ~]$ ping secure.clublog.org
PING secure.clublog.org (104.21.35.88) 56(84) tavua dataa.
64 tavua 104.21.35.88 (104.21.35.88):sta: icmp_seq=1 aika elää=58 aika=56.8 ms

This is very confusing and it would be nice to know what really is going on with Clublog servers.

--
Saku
OH1KH

F5JQF
Does not work for me either.

Hello Saku, Thank you for your answer. Something has changed on the side of ClubLog. I found some important information or not at all at this address.
https://clublog.freshdesk.com/support/solutions/articles/54906-how-to-up...
Maybe a start of an explanation? In the meantime, thank you for everything.
Best 73 Yves F5JQF

Yves, F5JQF
CQRlog Ver.2.6.0_(124)_GtK2 / Hamlib 4.5.5 / Linux Mint 21.3 Cinnamon
..

oh1kh
Clublog upload workaround

Tks Yves!

I will look that.
It looks like there is no change to parameters, but the address does not have the "secure." before clublog.org

If you can not get /etc/hosts entry work you could try my alpha test binary file. It has user changeable address in preferences/Online logs.
You find it from https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled Just download the newupdate.zip, extract it and start newupdate.sh in command console. It will do backups and update for you.

--
Saku
OH1KH

F5JQF
Tks Saku,

Tks Saku,
I am attaching the address again because I made a mistake in my previous message.

https://clublog.freshdesk.com/support/solutions/articles/54905-how-to-up...

------------
How To Upload Logs Directly Into Club Log Print
Modified on: Mon, 16 Jan, 2023 at 1:55 PM

As well as the main upload forms within the Club Log web site, there is another way to upload files directly which is designed to help developers wishing to add "Export to Club Log" features, or contesters and expeditioners who would like to have live logging updates to Club Log.

You can use HTTP POST to send ADIF files to https://clublog.org/putlogs.php. The POST form variables are as follows:

email: A registered email address in Club Log
password: The password to authenticate the email login (ideally, please ask the user to provide an Application Password from Club Log)
callsign: Optionally, the callsign into which the logs should be uploaded. If not set, the primary callsign of the account is used.
clear: If a value of 1 is given, the log will be flushed before the new upload is processed. In all other cases, including if this field is absent, the log will be merged.
file: A multipart/form-data upload which is used to POST the ADIF file with the form. The filename should be an ADIF, LGS or a ZIP file containing one of those.
api: An API key to access this interface (protecting it from abuse), which you can obtain by emailing the helpdesk.
For a working example, please view the source for https://clublog.org/test_upload.html.

When a file is passed to Club Log via this mechanism, it will be placed on the upload queue as normal. It is typically around 1 minute later that the upload will then be processed, so remember to allow for this extra delay, or longer at busiest times.

Successful uploads receive an HTTP response code 200, but you should also allow for error 403 codes, eg. if the credentials are wrong or the log has already been uploaded.

Example using cURL

#!/bin/bash

API='your-api-key-here'
PASS=your-app-password-here'
CALL='your-callsign-here'
FILE='/Users/michael/Desktop/example.adi'
EMAIL='michael@example.com'

curl -v -H "Content-Type: application/x-www-form-urlencoded" --data-urlencode adif@$FILE -d email=$EMAIL -d callsign=$CALL -d password=$PASS -d api=$API https://clublog.org/realtime.php

Note: as with all Curl commands you must escape content correctly, e.g. consider URL encoding. See https://everything.curl.dev/http/post/url-encode.

IMPORTANT: Please don't ever use putlogs.php to try and achieve "real-time" uploads, with just a handful of QSOs in each ADIF. There is a real time API designed for this purpose. Putlogs.php will block excessive uploads of small files misuse of this feature causes congestion for other, normal ADIF uploads. Additionally, repeated use of putlogs.php automatically delays uploads as a disincentive, and can even result in your IP address being firewalled. Thanks for your understanding: you should be using realtime.php if you are logging in realtime!

------------------------

All the best.

73 Yves F5JQF

Yves, F5JQF
CQRlog Ver.2.6.0_(124)_GtK2 / Hamlib 4.5.5 / Linux Mint 21.3 Cinnamon
..

F5JQF
problem solved

Hello Saku,
I took the time to install a clean system on a second SSD in dual boot.
The old OS LM 20.3 / CQRLog 2.6.0 (001). Everything is ok except the upload to ClubLog
The new OS LM 21.1 / CQRlog 2.6.0 (109) . Everything is ok including the upload to ClubLog.
The problem is solved.
I could not update GLIBC version 2.31 to 2.35 (risk of breaking the OS) too many applications were compiled before with version 2.31.
The easiest way was to redo a more recent installation.
Thank you again for all.

Best 73 Yves F5JQF

Yves, F5JQF
CQRlog Ver.2.6.0_(124)_GtK2 / Hamlib 4.5.5 / Linux Mint 21.3 Cinnamon
..

oh1kh
problem solved

OK Yves!
Fine!
The solution would have been to install "lazarus" to old GLIBC system and then download the source from github.com/OH1KH/cqrlog/tree/loc_testing as zip (or git clone) and issue
make && sudo make install
in unzipped cqrlog folder. That way the compile uses the current GLIBC of system.

Installing lazarus from package is quite straight and loads lots of needed dependencies at same time.
See:
New Ubuntu and latest cqrlog https://www.cqrlog.com/node/2984
Mint 20 Cinnamon and new cqrlog https://www.cqrlog.com/node/2998

But now you have also GLIBC up to date, hi.

--
Saku
OH1KH