No ticket matches when new tickets were added

[pawKer]

Hi! 👋 I was trying to set this up but unfortunately I have not been receiving any notifications from it while I was still getting the app notifications when new tickets were added :(

This is my config:

apiKey: <api-key> 

country: GB

notification:
  ntfy:
    url: ntfy.sh
    topic: <topic>
  telegram:
    token: <token>
    chatId: <chat-id>

global:
  regions:
    - GBNW 
    - GBNE
    - GBNO

  eventSimilarity: 0.85

tickets:
  - event: Deftones
  - event: Fontaines D.C.

And these are the logs from the Docker container:

2025/06/19 13:25:02 INFO Monitoring: Deftones, Fontaines D.C.

Have I misconfigured something or maybe they've changed something on their side?

[ahobsonsayers]

Hey! So it looks like you have set it all up correctly (assuming you set the API key) and I can confirm the app is still definitely working as I use it and get multiple notifications a day.

Let's see if we can identify the issue together then!

Two high level questions:

1. Are you on the latest release? I recently added some stuff that fixed some rate limiting issues I was seeing and (while unlikely) could be related
2. Can you give me any more info of what the notifications you got from twickets were? This might help us debug the issue.

An easy thing to try is to lower the similarity score. Maybe to something like 0.7, or possibly even lower, but bare in mind you might get some false positives. I'm not convinced this is the cause, but it's a good first step to try.

[pawKer]

Hi, thank you for the response! I have followed the instructions to get the API key and based on the logs I think it's working. I've also removed the regions for now.

1. Yep, should be, this is my docker-compose and I've done a re-pull now

services:
  twitchets:
    container_name: twitchets
    image: arranhs/twitchets:latest
    restart: unless-stopped
    volumes:
      - <hdd-location>:/twitchets

2. Here are some emails I got today while the container was running. I also got the push notifications on the app for these.

Since typing this reply and dropping the similarity to 0.5 I got this error log:

2025/06/22 16:27:27 INFO Found tickets for monitored event monitoredEventString=Deftones matchedEventName=Stereophonic numTickets=2 ticketPrice=£68.40 originalTicketPrice=£37.50 link=https://www.twickets.live/app/block/616052930517052,2

panic: runtime error: invalid memory address or nil pointer dereference

[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xbbb719]

goroutine 1 [running]:

heckel.io/ntfy/client.(*Client).expandTopicURL(0xc000047360, {0xc00044c390, 0x1f})

	/go/pkg/mod/heckel.io/ntfy@v1.31.0/client/client.go:226 +0xf9

heckel.io/ntfy/client.(*Client).PublishReader(0xd6e800?, {0xc00044c390?, 0xc000492a20?}, {0xf6e060, 0xc000046800}, {0xc00003f080, 0x3, 0xc00044c390?})

	/go/pkg/mod/heckel.io/ntfy@v1.31.0/client/client.go:99 +0x68

heckel.io/ntfy/client.(*Client).Publish(0xc000047360, {0xc00044c390, 0x1f}, {0xc000154002, 0xd0}, {0xc00003f080, 0x3, 0x3})

	/go/pkg/mod/heckel.io/ntfy@v1.31.0/client/client.go:87 +0xb8

github.com/ahobsonsayers/twitchets/notification.NtfyClient.SendTicketNotification({_, {_, _}, {_, _}, _}, {{0xc000013730, 0xf}, {{0x59a5380, 0xedfea25c7, ...}}, ...})

	/twitchets/notification/ntfy.go:40 +0x410

main.fetchAndProcessTickets(0xc00005e1b0, {{0xc0001e2900, 0x24}, {{0xe152ea, 0x2}}, {0xc00007eb00, 0x0, 0xc000110558}, {0x3fe0000000000000, {0x0, ...}, ...}, ...}, ...)

	/twitchets/main.go:147 +0xaf5

main.main()

	/twitchets/main.go:72 +0x510

Possibly something related to ntfy?

This was probably the misconifigured ntfy url, have changed it now to https://ntfy.sh and got some notifications (albeit not for the events I was tracking because of the similarity)

Also, it would be cool to have an environment variable to enable debug logs in the container to see the api response before and after filtering.

[ahobsonsayers]

Ahh good catch - if the https:// was missing this is very likely the cause of you not getting any notifications and also the panic. I should probably add a check for this!

If this is the cause, the logs should still show some tickets were matched - it looks like you did get this log before the panic? I have attached a screenshot below of what the log will looks like (Oasis for me). Did you also get a log for Fontaine's D.C.?

As for the debug logs - this is possible, but then you would get a wave of logs for every event that gets listed on Twickets. Is this what you want? I can imagine this would be too many logs 😅

I really appreciate you reporting this, because this does smell a little fishy, and its possible I just need a better URL check!

[ahobsonsayers]

As an aside - lowering your similarity to 0.5 is likely to make you get spammed with a lot of false positive notifications - like a lot.

I played around with this setting for a long time to settle on the default of 0.85 - and I generally don't recommend lowering it.

[pawKer]

Hey, I've been keeping this running for the past week or so and I'm definitely still getting more notifications from the official app.
My current theories for this are:

• I am running this on a VPS I had in a different country to avoid them blocking my actual IP so I wonder if that also is affecting things. Based on the logs it all looks ok now.
• Their live catalog only displays 10 results by default so if more than 10 tickets in GB are posted at the same time my tracked event may not make the cut
• Some other anti-automation measure they might have
• I'm not meant to go to these concerts 😂

[ahobsonsayers]

Hey, thanks for getting back to me - it's super helpful to get this feedback!

To address your points:

• This is great to hear that based on the logs the blocking by cloudflare looks to no longer be an issue - I'm super happy my fix worked!

• If more than 10 tickets come in at once, this actually shouldn't be an issue for twitchets - the application will keep loading past tickets until it finds a ticket it has already seen and then stop. By doing this it knows it's has found all new tickets since it last checked.

  Granted, it will only do for this up to 100 tickets, and given that it only scans every minute (to prevent rate limiting) I guess it could be possible that it will miss tickets if over 100 are listed in that minute.

  However I do actually have a log for exactly this - if twitchets fetches the max number of tickets allowed (100) and it does not see a ticket it has already seen, the warning will be logged. Assuming you are not seeing this log, I don't think we hre having this issue.

• This point has me thinking - it could be that as a way to prevent applications like this abusing the live feed, twickets actually does not add every single ticket that gets listed to the feed. Maybe it only adds a sub selection. If this is the case, this is really sad and I'm not sure what we can do about it 😫

• Everyone deserves to enjoy good music!

[ahobsonsayers]

One further thought - having read back over my code to see if I can identify any silly bugs, I might have noticed something suspicious.

In the notifications you are getting, are you getting any for tickets that are face value (or higher when fees are included), or are you only getting notifications for tickets that are below face value?

I'd find it super helpful to see a screenshot of some your past notifications in ntfy, or even a topic I can personally subscribe to to watch myself (which is coincidentally perfect because I love both Fontaines D.C. and Deftones too 😅)

[ahobsonsayers]

I have been doing a lot of work on this over the last two weeks and I believe I have solved this bug plus several others, along with some other nice improvements. Please pull the latest image and tell me how you get on.

As part of this, I have significantly improved the event matching algorithm, and I highly recommend removing any custom similarities you have set. If you remove them the default will be used, and this should be perfect for 99% if use cases - definitely for yours.

Thanks for the issue - looking forward to hearing if we fixed it!

[pawKer]

Hey @ahobsonsayers, sorry for going quiet, I left that reply and then went on holiday. Will pull the latest image and let you know how I get on! Thank you for all the effort you've put into this! In the meantime if you still need any screenshots for debugging let me know.

[hamperj]

Hi @ahobsonsayers Just wanted to chime in on this that I am also seeing an issue with getting any ticket matches, I have pulled the latest image and its still not working for me unfortunately.

For what its worth im trying to get Green Man 2025 tickets but I have also tried with more common ones like Drake/Kendrick and still no luck.

Here is my YAML:

apiKey: 83d6ec0c-54bb-4da3-b2a1-f3cb47b984f1 # REQUIRED: See README.md for details on how to obtain.

country: GB # Currently only GB is supported

notification:
  ntfy:
    url: https://ntfy.sh
    topic: greenmantickets

global:
  eventSimilarity: 0.85
  notification:
    - ntfy
  - event: Green Man 2025

Really appreciate what you've put together here, I have the Twickets push notification but they are no where near fast enough with my partner sometime getting them before me and visa vera

The one time I got something was when I put the evertSimilarity down to 0.5, it wasn't what I wanted but I could see the logs and the notification that something is working

Thanks again mate

[ahobsonsayers]

@pawKer - great, let me know how you get on

@hamperj - can you send me some logs? In fact can you set the DEBUG env var to true and confirm for me you are seeing tickets being picked up at all (you might need to wait a bit for a new listing - it will log every time it scans, and most of the time will fetch 0 new tickets)

[ahobsonsayers]

@hamperj - sorry I just looked at your yaml agaim and it looks like the structure is wrong?

Id expect it to look like this:

apiKey: api-key

country: GB # Currently only GB is supported

notification:
  ntfy:
    url: https://ntfy.sh
    topic: greenmantickets

global:
  eventSimilarity: 0.85
  notification:
    - ntfy

tickets:
  - event: Green Man 2025

[ahobsonsayers]

@hamperj did this solve your issue?