Support System Issues

[vetsols]

I am having trouble expediting a ticket. I am receiving this error:

Unhandled exception string: malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "Can't connect to sto...") at /home/support/lib/Tickets/Ticket/PurchasePrioritySupport.pm line 109.

 

[cPanelWilliam]

Hello! I'm sorry to hear about the issues with expediting your support request. Our internal team is currently investigating this issue. Can you let me know the ID of the support ticket that you opened?

 

[tommyxv]

Hello! I'm sorry to hear about the issues with expediting your support request. Our internal team is currently investigating this issue. Can you let me know the ID of the support ticket that you opened?

I'm getting the same error. #94468797

 

[tommyxv]

Added screenshot for reference.

 

[cPRex]

Hey there! Are you able to successfully update that ticket with a reply? If so, can you include this in the ticket so we can also investigate that? I did have our Customer Service team check your account but they didn't find anything out of the ordinary that would have led to this behavior, and I'm not seeing any general issues with the cPanel Store or with the priority support functions when I checked just now.

 

[tommyxv]

Hey there! Are you able to successfully update that ticket with a reply? If so, can you include this in the ticket so we can also investigate that? I did have our Customer Service team check your account but they didn't find anything out of the ordinary that would have led to this behavior, and I'm not seeing any general issues with the cPanel Store or with the priority support functions when I checked just now.

No issue updating the ticket with a reply.

 

[cPRex]

Interesting - I can't see much on my end for that, but please mention the priority bump issue in the ticket and they'll be able to look into that as well.

 

[tommyxv]

Interesting - I can't see much on my end for that, but please mention the priority bump issue in the ticket and they'll be able to look into that as well.

I posted a link to this thread in the ticket when I did the test reply to the ticket. Hopefully they are aware of it now.

 

[cPRex]

Update - we were able to reproduce the problem internally and our team is looking into this now.