uvdesk / community-skeleton

UVdesk Opensource Community Helpdesk Project built for all to make a Full Ticketing Support System along with many more other features.
https://www.uvdesk.com
MIT License
8.25k stars 456 forks source link

Version 1.0.18 not usabe, fatal server errors #495

Closed PeopleInside closed 2 years ago

PeopleInside commented 2 years ago

Thanks, for me the new version still generate a fatal error if the error page 404 is showed. After I click on a link in the 404 page my server give an error and helpdesk turn down.

I do this: After following all updating instruction given by you I try to load an inexistent URL like https://helpdesk.peopleinside.it/it/dtrtrt than I click on one of the links in the new 404 page and server get down with a fatal error.

uvdesk new error

https://github.com/uvdesk/community-skeleton/discussions/493

PeopleInside commented 2 years ago

The error can be resolved temporarily by running the cache clear problem but can be generated again by following the steps showed above but also without following this step the system will be broken again shortly.

papnoisanjeev commented 2 years ago

@PeopleInside

It may be your server error if your server going down time to time. Normally if there is any error related to project it will show you custom error page of project.

You can try on your localhost as well.

PeopleInside commented 2 years ago

@papnoisanjeev

It may be your server error if your server going down time to time.

Is not my server, all works fine just the new version of UVdesk is not working. Can be something maybe in my server not compatible with UVdesk new version and I need help to understand why, this issue happen just in the new UVdesk version.

I have also a open ticket with you #26712

I'm also trying to investigate with the control panel team, Webuzo... but again all websites work fine, is just the new version of UVdesk that is giving issues.

As you can see:

https://www.peopleinside.it/ (works) https://helpdesk.peopleinside.it/it/ (works) https://helpdesk.peopleinside.it/uvdesknew/public/en/ (broken)

papnoisanjeev commented 2 years ago

@PeopleInside

Try this https://helpdesk.peopleinside.it/uvdesk/public/en/

May be you are opening a wrong link with uvdesknew in URL and folder does not exist on your server. Also test with incognito tab.

PeopleInside commented 2 years ago

@papnoisanjeev actually my help desk at the address you provided in above previous message is using the version 1.0.16

You can see the new version here: https://helpdesk.peopleinside.it/uvdesknew/public/it/ and is not working. As soon I upgraded I was able to load that page but after click the link in 404 now it gives error.

papnoisanjeev commented 2 years ago

@PeopleInside

Make your project env to dev so that we can check your error.

PeopleInside commented 2 years ago

Done

https://helpdesk.peopleinside.it/uvdesknew/public/it/ytgftr

papnoisanjeev commented 2 years ago

@PeopleInside

Above exception is fine which comes when you are accessing a route which is not exist.

Please try with a fresh install if you are facing the same issue or not.

PeopleInside commented 2 years ago

@papnoisanjeev I tried to update with composer create-project uvdesk/community-skeleton helpdesk-project that create a new project. also there same issue

I can see exist also this error:

Immagine 2021-10-28 133651

papnoisanjeev commented 2 years ago

@PeopleInside

It is also not an issue just showing that translation is not working for this sentence.

It there is any error header of the above page will show red which is green currently.

PeopleInside commented 2 years ago

@papnoisanjeev in the ticket #26712 you can read server error log. Now I am also waiting a reply from Webuzo team, they can take long time before reply. I will try to continue to alert Webuzo team to reply about this issue just to check why I'm having 50 X error. Thanks, for now I will keep this issue opened until will be not resolved.

I will update you in the case is not a control panel issue.

PeopleInside commented 2 years ago

No reply from Webuzo, I need wait. In the main time I tried a new install and issue is the same

Immagine 2021-10-28 162214

I don't know why this issue is present only on UVdesk and on the new UVdesk version, not in 1.0.6 What I need investigate with Webuzo team is if the 50 X error is an error that is generated because something in PHP or PHP extension is bugged.

I need wait the control panel team for look into this. The server error log seems say: Apache Error ‘Failed to read FastCGI header

PeopleInside commented 2 years ago

The 50 X error happen only on prod mode, not in dev mode. Why?

PeopleInside commented 2 years ago

I'm closing this issue for now also if is not resolved.

The reason why I do this is because I will diagnose with Webuzo team as the error seems to be from Webuzo and here seems I'm not getting useful info on why I'm facing this.

PeopleInside commented 2 years ago

The Webuzo team tested the new version of Uvdesk and told me they get the same issue on Cpanel so they suggest to report the issue to you.

komal-sh-27 commented 2 years ago

@PeopleInside I have tested with prod mode but here are not showing this type of issue or errors on the 404 page not found.

You can see here: https://www.loom.com/share/4b99694d96e34770be54388b8bb67f1f

PeopleInside commented 2 years ago

@Komal-sharma-2712 thank you but what I can do now?

I forwarded this issue to the Webuzo team, they said the issue if from UVdesk and they was able to reproduce the issue also on CPanel.

Webuzo say is UVdesk, you show me no issue in UVdesk so what I should do, not upgrade and still run an old version?

UVdesk tested in localhost by you with what version of PHP? Under Apache?

In any case I need run on a server not on localhost. I'm not new in UVdesk so I'm just reporting I'm unable to upgrade, even new installation from Softaculous installer give error, see UVdesk ticket N #26712

I need a solution. I don't think the error is generated by the 404 page, also loading sometime the main address cause the issue.. I just showed you how I'm able to reproduce the issue. In the UVdesk ticket mentioned you can see also issue from a new installation by Softaculous script installer.

PeopleInside commented 2 years ago

I'm running PHP 7.4.24 Now the issue can be from PHP or from UVdesk.

I need understand this and how I can resolve. Unfortunately Webuzo doesn't yet allow me to install PHP 8.0 so I cannot test with a different supported PHP version.

The error server log say: [proxy_fcgi:error] [pid 20263] (104)Connection reset by peer: AH01075: Error dispatching request to : [proxy_fcgi:error] [pid 20263] [client ****:56025] AH01067: Failed to read FastCGI header

PeopleInside commented 2 years ago

There is a particular new Apache, PHP requirements for UVdesk 1.0.18 that was not necessary in UVdesk 1.0.16? I still be in touch with the Webuzo team that I understand continue to think the issue is in UVdesk.

Is a real strange issue, all works on my server except UVdesk 1.0.18 The error seems to be a Webuzo 50 X error but they said also on CPanel there is a 503 server error.

You show no issue on localhost but I don't know what version of PHP are you using. In any case I need help to resolve the issue to be able to upgrade to the latest UVdesk version.

komal-sh-27 commented 2 years ago

I used PHP version 7.4.22 and apache version: Apache/2.4.41

PeopleInside commented 2 years ago

Hum maybe is possible to test with PHP 7.4.24? I tried but in localhost I still get php PHP Mailparse error even if I followed guide to install on Windows xamp.

But also if in that case all works I still need help because I need upgrade UVdesk and due to the 50 X error on Webuzo I'm unable to do.

So actually webuzo team say the issue is UVdesk and UVdesk say all is fine. Results.. I'm unable to use latest version of UVdesk.

I need find help and solution to this.

PeopleInside commented 2 years ago

I hope in some help from you or I need find an alternative version in the future if I still be not able to resolve this. Also... I'm not reeving no more, since weeks, email notifications when you reply to the ticket #26712 so you should have some issue in email configuration or in spam score.

komal-sh-27 commented 2 years ago

@PeopleInside our team working on that issue and ticket and we will resolve it as soon as possible.

our team will reply you soon.

PeopleInside commented 2 years ago

@Komal-sharma-2712 ok thanks. Unfortunately seems when you reply to that ticket I get no email so your outgoing email has spam issue or something is broken. I tested the reset password on your ticket system and I get the email. I will monitor the ticket online :) Thanks.

For now if you where not able to reproduce the issue I reported here, you cannot resolve. This is my worry but I hope you will understand and fix what is wrong. Thanks again.

PeopleInside commented 2 years ago

Just for information, in dev mode on V 1.0.18 I'm unable to get 50 X error. In prod mode I'm able to get always this error even navigating the operator panel... just clic some link and get server error while in dev mode not.

PeopleInside commented 2 years ago

uvdesk18 bugged prod

PeopleInside commented 2 years ago

The issue seems to be from Webuzo side as UVdesk team has showed all works fine on locale and on the server. Sorry... I will write again to the Webuzo team where seems hard to get support for this issue.

PeopleInside commented 2 years ago

This issue seems to be caused by PHP 7.4.24 used by Webuzo. I suppose Webuzo team need upgrade PHP to the latest PHP 7.4.25

In my test with PHP 7.3 that I cannot run because is no more supported by other app I use, UVdesk 1.0.18 seems to work fine

PeopleInside commented 2 years ago

Webuzo team tested with PHP 7.4.25 also on CPanel and they say the error persist so the issue seems to be in UVdesk. Also is curios to see that on dev mode the issue is not present.

PeopleInside commented 2 years ago

Seems this issue as other issue will be not resolved or maybe will require a long time for be resolved.

A strong issue is regarding duplicate ticket, issue not resolved. Another important issue is that delete email are forever and are not moved to trash, this is another issue opened and another important issue is that there is no way to have sent email from UVdesk to be avaiable in the sent folder.

How about this issue to be unable for almost a month to update to the latest version of UVdesk?

Now, I'm using the Webuzo control panel and not only mi install of UVdesk 1.0.18 is not working but also creating a new install from Softacolous panel, it give the same exact issue confirmed also from the Webuzo team panel staff.

If I'm not wrong, if I never missunderstood, the Webuzo team are able to reproduce the issue also on the CPanel so not only in Webuzo Control panel.

This let me think the issue is of UVdesk also because I have no issue in the old installation 1.0.16 where all works fine so how can be an issue of my server?

In the other hands maybe I tested UVdesk 1.0.18 with PHP 7.3 (that is old and should not be used) and the error seems is not present, also if I turn UVdesk into dev mode, the error is not present. This let me think the issue can be the PHP version on the first case and on the second let me think something is wrong in UVdesk that work on dev but not on prod.

As you can understand I cannot give full VPS access to diagnose this issue so, as I don't see any solution, any light I suppose this will be the end of the story: I need find another software solution for manage my ticket.

Really sad. Instead of asking full access to my server, you need to consider to give remote support, this will allow you to see the issue on the customer, user PC without getting full access to the server where you also are taking a big responsability in the case you do any damage when admin cannot check what you are doing on his server.

I'm really sad to see this issue and other issues ... issue that are most important, still be frozen. UVdesk is nice but strong issues should be resolved and not after too many months or to be kept unresolved.

PeopleInside commented 2 years ago

Resolved with your support and PHP 8.0