Potential iPV6 issue with osTicket 1.6

mambobrown

I ran into the problem where osTicket could not store an IPv6 address in these tables (osTicket would not update and sent the bad insert query with the IPv6 address to my maintenance support email):

ost_ticket_response

ost_ticket_message

ost_ticket

ost_syslog

ost_api_key

So, I increased the ip_address fields in each of the tables listed above. I don't really consider this a bug but I didn't know where to put it. Hopefully, one of the team members will get a hold of this message and correct the potential issue.

ntozier

Thanks for sharing. :)

Kelli

Thanks for pointing this out to us. :)

Soultripper

Same issue...but should this be addressed by now

Hi,

I am getting the same problem creating a ticket as I have IPv6 still enabled:

Data too long for column 'ip_address' at row 1

However, shouldn't this be addressed already in the current release:? Is modifying the column widths the correct solution at this stage?

Using osTicket 1.6.0

So far, the product seems great, just having some teething problems with the outgoing emails from our internal server.

Kindest Regards

Sky