Non-helpful error message when IP address already exists in list

AI-generated summary

The discussion revolves around a non-helpful error message encountered when attempting to add an IP address to the screened IP’s list, only to discover that the IP was already present in the list. jomaxro initially encountered the issue and received an uninformative error message (Sorry, an error has occurred.), which led to further investigation. cpradio suggested that the IP might already be in the list or be captured by a rollup rule, prompting jomaxro to search for the IP and confirm its presence. It is proposed that a better error message, one that informs users that the IP already exists on the list, would be more helpful in such situations.

Update: Turns out the IPs were already in the list, but searching for only the first byte of the address, not all 4 would have search say “no results”. The error message should instead inform you that the IP is on the list already, and searching with only the first 3 digits of the IP should work.


Our newest moderator didn’t read the delete user dialog properly and thus did not block IPs for a few of our recent spammers. I attempted to add them manually to the screened IP’s list, and got the non-descriptive error Sorry, an error has occurred..

Looking at the console, I see the following:

ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:3 
POST
http://discourse.stonehearth.net/admin/logs/screened_ip_addresses.json
500 (Internal Server Error)
send @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:3
ajax @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:3
e @ application-68c6d08b0bee69dc1f8870c145e27753885b9d561bcef85076110e89ccf79c6e.js:1
_ @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:16
h @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:16
a @ application-68c6d08b0bee69dc1f8870c145e27753885b9d561bcef85076110e89ccf79c6e.js:1
value @ admin-6a4dbcad6f35782f7ee229b7692cac7097982d8bfe86e3c44a9315c0850af7db.js:1
submit @ admin-6a4dbcad6f35782f7ee229b7692cac7097982d8bfe86e3c44a9315c0850af7db.js:3
send @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:13
r @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:8
triggerAction @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:11
sendAction @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:13
value @ application-68c6d08b0bee69dc1f8870c145e27753885b9d561bcef85076110e89ccf79c6e.js:16
trigger @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:14
r @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:8
handleEvent @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:14
handleEvent @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:14
run @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:3
join @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:3
u.join @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:8
_bubbleEvent @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:13
(anonymous function) @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:13
dispatch @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:2
v.handle @ ember_jquery-c9524b48466ee05bcf3f9ddaf05405387eb17017e61e90e76628f989db37eb4e.js:2
1 Mi Piace

Chances are, it already exists in the list then. Or is captured via a Rollup rule. As I can add new IPs just fine on my sandbox instance.

See if searching for the IP makes it show up, and then gradually remove parts of the IP to check if there are rollup rules

Could it be that I’m a moderator?

Scratch that, they’re already on the list. Interestingly searching for the first 8 bytes of the address only failed - but they’re there. Need a better error message here!

3 Mi Piace