Unable to add Q Feed IPs to my firewall rules.

Started by lionflower, February 06, 2026, 10:04:58 PM

Previous topic - Next topic
Print
Go Down Pages1
User actions
February 06, 2026, 10:04:58 PM
Just signed up for Q Feed today and have downloaded the plugin and added my api key etc. However when I try to use q feed as destination in my rules i get "__qfeeds_malware_ip is not a valid source IP address or alias."

If I go to Firewall - Diagnostics - Aliases - __qfeeds_malware_ip it lists a lot of IP addresses so I don't think there is an issue there. I am on 26.1.1

Any ideas?
February 06, 2026, 11:05:54 PM #1
Update: Just rebooting the firewall seemed to fix this issue.
February 07, 2026, 02:00:17 PM #2
Glad it's working again after the reboot! We're curious though if more users have experienced this?

|  Your Threat Intelligence Partner  |  qfeeds.com
February 09, 2026, 11:34:46 PM #3
Quote from: lionflower on February 06, 2026, 11:05:54 PMUpdate: Just rebooting the firewall seemed to fix this issue.
Quote from: Q-Feeds on February 07, 2026, 02:00:17 PMGlad it's working again after the reboot! We're curious though if more users have experienced this?
Thanks, that is true, I had the same error, rebooted (thanks lionflower) it is fine now. This was a new clean install of V26.1.1 on hardware.
February 10, 2026, 02:12:52 PM #4
We might have found the culprit. It was most likely due to a 'NULL' response from our server in one of the values of the license check. If anyone needs help, shoot us a message ;-)

|  Your Threat Intelligence Partner  |  qfeeds.com
February 24, 2026, 06:39:13 PM #5
Quote from: Q-Feeds on February 07, 2026, 02:00:17 PMGlad it's working again after the reboot! We're curious though if more users have experienced this?

I'm experiencing this issue right now. Unfortunately I can't reboot until later. Will write back if rebooting helps.
February 24, 2026, 07:15:47 PM #6
Quote from: requird on February 24, 2026, 06:39:13 PMI'm experiencing this issue right now. Unfortunately I can't reboot until later. Will write back if rebooting helps.

Was able to do a reboot and it solved the issue.
February 26, 2026, 09:29:28 PM #7
Quote from: requird on February 24, 2026, 07:15:47 PM
Quote from: requird on February 24, 2026, 06:39:13 PMI'm experiencing this issue right now. Unfortunately I can't reboot until later. Will write back if rebooting helps.

Was able to do a reboot and it solved the issue.

Can you tell me which version you're running?

|  Your Threat Intelligence Partner  |  qfeeds.com
March 06, 2026, 08:20:37 AM #8 Last Edit: March 06, 2026, 12:35:38 PM by nicospavlou
Hello,

Had the same issue and when I rebooted, after everything was working fine.

OPNsense Version 26.1.3
 
Cheers,
Nicos
March 06, 2026, 09:58:58 PM #9
Thx! We've found the problem and will be solved soon: https://github.com/opnsense/plugins/issues/5288
Seems a combination of the core and our plugin ;)

|  Your Threat Intelligence Partner  |  qfeeds.com
Print
Go Up Pages1
User actions