Fixed XenForo tries to send push notifications to invalid URLs

K

Kirby

Well-known member

• Nov 27, 2025

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #1

Affected version

2.3.7

I havn't found a definitive reference for this yet, but it seems that Chrome / Chromium sometimes generates placeholder URLs starting with https://permanently-removed.invalid/fcm/send for invalid / expired push subscriptions, see https://xenforo.com/community/threads/push-notification-failure-curl-error-6.234166

XenForo currently accepts those URLs and tries to send notifications there which obviously fails and kinda floods the error log if those endpoints are utilized frequently (which happened to us yesterday).

Suggested Fix
Ignore endpoint URLs starting with https://permanently-removed.invalid/ in first place, eg. don't even store them in DB by returning false for such URLs in UserPushRepository::validateSubscriptionDetails

 

Last edited: Nov 27, 2025

webbouk

Well-known member

• Dec 1, 2025

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #2

Yeap, got the same, random threads, and varying amounts of errors daily...

example:

 

XF Bug Bot

XenForo bug fixer bot

Staff member

• Dec 1, 2025

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #3

Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future XF release (2.3.8).

Change log:

Inhibit sending push notifications to permanently removed Chrome subscriptions

Click to expand...

There may be a delay before changes are rolled out to the XenForo Community.

 

webbouk

Well-known member

• Dec 1, 2025

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #4

Any chance of a quick-fix whilst waiting for the 2.3.8 release?

 

K

Kirby

Well-known member

• Dec 1, 2025

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #5

* Untested *

 

Attachments

• UserPushRepository.diff

  456 bytes · Views: 25

webbouk

Well-known member

• Dec 2, 2025

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #6

@Kirby ^^^ This appears to fix the issue. No errors received since making the changes

 

webbouk

Well-known member

• Dec 4, 2025

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #7

@Kirby, unfortunately I have to report that it didn't last long and numerous error messages have still been generated....

 

K

Kirby

Well-known member

• Dec 5, 2025

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #8

Did you delete invalid entries from the DB when you applied the patch?
The patch does not affect existing entries, it should only prevent new ones from being accepted.

 

webbouk

Well-known member

• Jan 9, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #9

Kirby said:

Did you delete invalid entries from the DB when you applied the patch?
The patch does not affect existing entries, it should only prevent new ones from being accepted.

Click to expand...

Apologies for the delay in getting back to this @Kirby

Please can you explain how to delete invalid entries from the DB

Thanks

 

K

Kirby

Well-known member

• Jan 9, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #10

K

XF 2.3 Post in thread 'Push notification failure: cURL error 6'

Nov 11, 2025

SELECT * FROM xf_user_push_subscription WHERE endpoint LIKE 'https://permanently-removed.invalid%'

Does that return results?
If so, delete the records - those are invalid / removed push subscriptions.

• Kirby

• 

 

webbouk

Well-known member

• Jan 9, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #11

Thanks @Kirby , two records returned and deleted

 

K

Kirby

Well-known member

• Jan 9, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #12

Great

So if the patch works no new invalid entries should be created.

 

webbouk

Well-known member

• Jan 10, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #13

No new ones overnight, ie past twelve hours, so it looks to be working

 

AndreaMarucci

Well-known member

• Jan 11, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #14

Kirby said:

* Untested *

Click to expand...

Can you please indicate how to apply this patch waiting for 2.3.8?

 

K

Kirby

Well-known member

• Jan 11, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #15

There are many tools that can apply patches in unified diff format (that's basically the standard).

Ask your favourite search engine or AI assistant how to do that.

Or as the patch is really simple you can even open the diff in your favourite editor and apply the change manually.

 

Last edited: Jan 11, 2026

Charlie G

Active member

• Jan 13, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #16

Kirby said:

There are many tools that can apply patches in unified diff format (that's basically the standard).

Ask your favourite search engine or AI assistant how to do that.

Or as the patch is really simple you can even open the diff in your favourite editor and apply the change manually.

Click to expand...

I seem to have failed at both of those

 

AndreaMarucci

Well-known member

• Jan 13, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #17

I'll wait for the official patch since I'm not a coder and I'm not able to apply such a patch...

 

webbouk

Well-known member

• Jan 13, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #18

Have you got access to your forum files?

 

Charlie G

Active member

• Jan 13, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #19

webbouk said:

Have you got access to your forum files?

Click to expand...

If you are asking me, yes.

 

AndreaMarucci

Well-known member

• Jan 13, 2026

• %22 data-success="Embed code HTML copied to clipboard." class="">
• #20

Me too...