spotweb: [New issue] Black- and whitelists are not working anymore, seem to be garbled?
Describe the bug/issue
- Both black- and whitelists are garbled nowadays (probably encrypted), the lists are unusable to Spotweb currently, resulting in
Non-fatal: Updating black/whitelist failed, most likely unreachable!error messages upon retrieving of Spots.
Have you searched the internet or Github for an answer?
- I have found issue https://github.com/spotweb/spotweb/issues/833, which said “use these new .TK links”, but these exact same links give the garbled black- and whitelists.
- The links are working perfectly fine, as they both return
HTTP 200headers.
To Reproduce
- Go to ‘http://spotlist.tk/spotnet/whitelist.xml’ and/or ‘http://spotlist.tk/spotnet/blacklist.xml’ with a browser and see the garbled XML-files.
Expected behavior
- Working black- and whitelists
Desktop (please complete the following information):
Latest Docker container from jgeusebroek/spotweb, it uses PHP version 8.1.27.
About this issue
- Original URL
- State: closed
- Created 3 months ago
- Comments: 22
Found the problem. Solved. You can also use https now. @Sweepr spotweb uses the xml format (same as spotnet) because those are the only lists actively maintained.
Which settings should I check, as I don’t have a clue. I see I also have the same docker image you have. 😃 Never mind: I already found it: for some reason in Spotweb itself, the link was still HTTPS, whereas when I checked with DBeaver it was already HTTP:
Finished updating blacklist. Added 22, removed 1, skipped 7 of 1102 lines. Finished updating whitelist. Added 3, removed 0, skipped 6 of 915 lines.The xml is file but https doesn’t work. I will look into that.