Here is a bit of SQL to run if your site has been spitting out errors like:
Message: Data too long for column 'poster_ip' at row 1
That error will show up if the users IP is being collected as an IPv6 number and not and IPv4. What is the difference, without getting into it too much, I will show you a visual difference:
IPv6: 2803:7081:6800:6f4e:7ce2:ad68:487a:c17
IPv4: 127.124.053.244
So, this SQL, just makes the table to accept more characters, so you can stuff the IPv6 into the spot that once help only IPv4 addresses.
Just run this bit of SQL, and that's it, (for now).
CodeSelect all
ALTER TABLE `nuke_bbbanlist` CHANGE `ban_ip` `ban_ip` VARCHAR(128);
ALTER TABLE `nuke_bblogs` CHANGE `user_ip` `user_ip` VARCHAR(128);
ALTER TABLE `nuke_bbposts` CHANGE `poster_ip` `poster_ip` VARCHAR(128);
ALTER TABLE `nuke_bbprivmsgs` CHANGE `privmsgs_ip` `privmsgs_ip` VARCHAR(128);
ALTER TABLE `nuke_bbprivmsgs_archive` CHANGE `privmsgs_ip` `privmsgs_ip` VARCHAR(128);
ALTER TABLE `nuke_bbsessions` CHANGE `session_ip` `session_ip` VARCHAR(128);
ALTER TABLE `nuke_bbsessions_keys` CHANGE `last_ip` `last_ip` VARCHAR(128);
ALTER TABLE `nuke_honeypot` CHANGE `ip` `ip` VARCHAR(128);
ALTER TABLE `nuke_link_us` CHANGE `user_ip` `user_ip` VARCHAR(128);
ALTER TABLE `nuke_nsnsp_sites` CHANGE `user_ip` `user_ip` VARCHAR(128);
ALTER TABLE `nuke_nsnst_blocked_ips` CHANGE `ip_addr` `ip_addr` VARCHAR(128);
ALTER TABLE `nuke_poll_check` CHANGE `ip` `ip` VARCHAR(128);
ALTER TABLE `nuke_shoutbox_shouts` CHANGE `ip` `ip` VARCHAR(128);
ALTER TABLE `nuke_users` CHANGE `last_ip` `last_ip` VARCHAR(128);

