Cloudlog and sync LoTW

[myhobby2]

Until early this year sync with LoTW was working but today I can't get it sync-ed anymore. Deleted the .p12 certificate and reinstalled it and now states: status = valid / last upload = not synced. When I use the button MANUAL SYNC nothing improves.

Just updated to the latest release today. Does anyone has encountered a similar situation (and is there a solution?)

[magicbug]

The fact the callsign and dxcc is empty suggests a problem. I'd suggest deleting it from the system, making sure tQSL is up to date on your computer and then exporting a new p12

[myhobby2]

That is done by my with a purpose. There is a callsign and DXCC available ;-) and I already did beforehand what you suggested.

[magicbug]

Is the callsign and DXCC displayed now within the table now?

If not, we will need to enable logging /application/config/config.php and then reupload the certificate and provide the output in /application/logs so that it can be investigated further.

[geogarden]

I have the same problem, it doesn't show me the status synchronized

[myhobby2]

ERROR - 2024-01-30 14:43:17 --> Severity: Warning --> fopen(./uploads/lotw/on3???-2024-01-30-14-43-17-cloudlog.tq8): Failed to open stream: Permission denied /var/www/cloudlog/application/controllers/Lotw.php 275
ERROR - 2024-01-30 14:43:17 --> Severity: error --> Exception: fwrite(): Argument #1 ($stream) must be of type resource, bool given /var/www/cloudlog/application/controllers/Lotw.php 276

I editted my callsign because it is not relevant to the issue.

[myhobby2]

As extra info: Linux cloudlog 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64

[magicbug]

Looks like /uploads folder permissions are incorrectly setup

[myhobby2]

your were right but let me explain what I did
/var/www/cloudlog/uploads/ was 0775 and I changed it to 0777. Only for this directory

I never touched any of these permissions, knowing what the consequences are. I did do twice an upgrade via the script in /var/www/cloudlog/update_cloudlog.sh. No idea, but just a clue.

It works again after this permission change, but you can help me by providing the correct permission ;-)

[myhobby2]

Thanks for the help before I forget to mention this! Very much appreciated