"Add my current ip" and "un-ban XX ip" button to the ip exception page for MySQL access.
Hi, I often have to update my ip in the MySQL authorized access list and
it would be a great addition to have a simple "add my current ip"
button on that page. I don't know how many we are doing this but I guess
i'm not the only one :)
Another thing would be a possibility to
"un-ban" an ip from this page. My ip changes randomly from time to time
and I often get ban when the program I access the database with access
the SQL too many times after my IP change. Adding the new good IP to the
exception list doesn't seem to unban me and I always have to contact my
service provider to un-ban me. I guess they run some kind of "flush" at
the ip list. Could this also be a function added to the page? I mean
the possibility to unlock a banned IP? I have no clue if it's something
possible, but it would be useful!
Thanks a lot
Definitely sounds like a reasonable idea to have a button that can pre-fill the IP address/host of the individual viewing the page. I know in many cases this would satisfy a lot of use cases.
The request to "un-ban" an IP is something that I hesitate with, however. What you're referencing is when a host runs the statement "FLUSH PRIVILEGES" and/or "FLUSH HOSTS" which lifts the blocks for relevant login/host connection failures by flushing the cache entirely.
This is only possible when the MySQL user has the "RELOAD" privilege. This is not historically given to the cPanel user. One of the reasons is simply because of the nature of FLUSH, you're dropping various MySQL caches which will have to be rebuilt.
I'd like to hear further feedback on this from providers on if they feel this is something they'd be comfortable giving to end users.
Definitely sounds like a reasonable idea to have a button that can pre-fill the IP address/host of the individual viewing the page. I know in many cases this would satisfy a lot of use cases.
The request to "un-ban" an IP is something that I hesitate with, however. What you're referencing is when a host runs the statement "FLUSH PRIVILEGES" and/or "FLUSH HOSTS" which lifts the blocks for relevant login/host connection failures by flushing the cache entirely.
This is only possible when the MySQL user has the "RELOAD" privilege. This is not historically given to the cPanel user. One of the reasons is simply because of the nature of FLUSH, you're dropping various MySQL caches which will have to be rebuilt.
I'd like to hear further feedback on this from providers on if they feel this is something they'd be comfortable giving to end users.
Definitely sounds like a reasonable idea to have a button that can pre-fill the IP address/host of the individual viewing the page. I know in many cases this would satisfy a lot of use cases.
The request to "un-ban" an IP is something that I hesitate with, however. What you're referencing is when a host runs the statement "FLUSH PRIVILEGES" and/or "FLUSH HOSTS" which lifts the blocks for relevant login/host connection failures by flushing the cache entirely.
This is only possible when the MySQL user has the "RELOAD" privilege. This is not historically given to the cPanel user. One of the reasons is simply because of the nature of FLUSH, you're dropping various MySQL caches which will have to be rebuilt.
I'd like to hear further feedback on this from providers on if they feel this is something they'd be comfortable giving to end users.
Definitely sounds like a reasonable idea to have a button that can pre-fill the IP address/host of the individual viewing the page. I know in many cases this would satisfy a lot of use cases.
The request to "un-ban" an IP is something that I hesitate with, however. What you're referencing is when a host runs the statement "FLUSH PRIVILEGES" and/or "FLUSH HOSTS" which lifts the blocks for relevant login/host connection failures by flushing the cache entirely.
This is only possible when the MySQL user has the "RELOAD" privilege. This is not historically given to the cPanel user. One of the reasons is simply because of the nature of FLUSH, you're dropping various MySQL caches which will have to be rebuilt.
I'd like to hear further feedback on this from providers on if they feel this is something they'd be comfortable giving to end users.
Replies have been locked on this page!