🔴 January 2024 Alert: Forum support inactive!
New forum registration are currently closed.
Use GitHub discussions
.

    UVdesk

    • Login
    • Search
    • Recent
    1. Home
    2. escozul
    3. Posts
    E
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 13
    • Best 0
    • Controversial 0
    • Groups 0

    Posts made by escozul

    • RE: Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      @peopleinside Than you for replying. Freescout seems free... Maybe the modules are paid but the core seems free. UVdesk plugins are also paid for so I guess it's kind of the same...

      That's a nice alternative. Since it's self-hosted, I might give it a go!

      posted in Technical Help
      E
      escozul
    • RE: Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      @peopleinside Hello,

      Did you migrate to a different solution? Do you mind sharing it?

      posted in Technical Help
      E
      escozul
    • RE: Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      @leooxx Hello,
      I can't find that entry on any of my logs. How do you know that the error is with the php-mailparse addon?

      cause running PHP -m lists mailparse right there..

      You mentioned a "logs app"... Can't find that.

      posted in Technical Help
      E
      escozul
    • RE: Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      @leooxx Thank you.

      Will try that on Tuesday and get back here to post if it's resolved or not.

      posted in Technical Help
      E
      escozul
    • RE: Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      @peopleinside
      Thank you for your time.
      I appreciate all your help.

      Well.. Let's hope that in the following days, someone will come across this issue and help me resolve it.

      posted in Technical Help
      E
      escozul
    • RE: Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      @peopleinside

      Thank you. Same error though.

      posted in Technical Help
      E
      escozul
    • RE: Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      @peopleinside
      Hello
      in my .env, I see the following:

      ###> symfony/framework-bundle ###
      APP_ENV=dev
      APP_SECRET=YOUR_APP_SECRET
      

      Is that correct? Should I have set the app secret somewhere? ... or it does not matter?

      My uvdesk.yaml:

      parameters:
          app_locales: en|fr|it|de|da|ar|es|tr|zh|pl
          
          # Default Assets
          assets_default_agent_profile_image_path: 'bundles/uvdeskcoreframework/images/uv-avatar-batman.png'
          assets_default_customer_profile_image_path: 'bundles/uvdeskcoreframework/images/uv-avatar-ironman.png'
          assets_default_helpdesk_profile_image_path: 'bundles/uvdeskcoreframework/images/uv-avatar-uvdesk.png'
      
          uvdesk_site_path.member_prefix: --------- #Masked for security
          uvdesk_site_path.knowledgebase_customer_prefix: --------- #Masked for security
          
          # File uploads constraints
          # @TODO: Set these parameters via compilers
          max_post_size: 8388608
          max_file_uploads: 20
          upload_max_filesize: 2097152
      
      uvdesk:
          site_url: 'helpdes.mydomain.com' # No /public here. It's properly set.
          upload_manager:
              id: Webkul\UVDesk\CoreFrameworkBundle\FileSystem\UploadManagers\Localhost
          
          support_email:
              id: email@mydomain.com #properly set to my domain. Changed it for security purposes
              name: Support HelpDesk
              mailer_id: mailer_SES
          
          # Default resources
          default:
              ticket:
                  type: support
                  status: open
                  priority: low
              templates:
                  email: mail.html.twig
      

      Tried to mask some. Sorry for that. They seem just fine though.

      Edit:

      I visited the address found here: API https://uvdesk.example.com/mailbox/listener
      kept bugging me.

      The result on screen was:
      {"success":false,"message":"Request not supported."}
      Have no idea what that is! what is it?
      What about the API? When I go over to settings, the first selection is the API:
      alt text

      I haven't used that access token anywhere. What's it for? Should I put it in the .env file?

      posted in Technical Help
      E
      escozul
    • RE: Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      @peopleinside
      Thank you for all these topics. Still browsing through them to figure out if there is a similar resolution. In my case the call to https is made properly so I don't think the issue is there.

      Also I went over to the logs and captured all the errors and warnings that come up when I try to fetch the emails. Here are my logs:

      [2023-12-12T14:47:44.439482+01:00] deprecation.INFO: User Deprecated: Method "Symfony\Component\HttpKernel\Bundle\Bundle::getContainerExtension()" might add "?ExtensionInterface" as a native return type declaration in the future. Do the same in child class "Webkul\UVDesk\CoreFrameworkBundle\UVDeskCoreFrameworkBundle" now to avoid errors or add an explicit @return annotation to suppress this message. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Method \"Symfony\\Component\\HttpKernel\\Bundle\\Bundle::getContainerExtension()\" might add \"?ExtensionInterface\" as a native return type declaration in the future. Do the same in child class \"Webkul\\UVDesk\\CoreFrameworkBundle\\UVDeskCoreFrameworkBundle\" now to avoid errors or add an explicit @return annotation to suppress this message. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/vendor/symfony/error-handler/DebugClassLoader.php:331)"} []
      [2023-12-12T14:47:44.440761+01:00] deprecation.INFO: User Deprecated: Method "Symfony\Component\HttpKernel\Bundle\Bundle::getContainerExtension()" might add "?ExtensionInterface" as a native return type declaration in the future. Do the same in child class "Webkul\UVDesk\AutomationBundle\UVDeskAutomationBundle" now to avoid errors or add an explicit @return annotation to suppress this message. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Method \"Symfony\\Component\\HttpKernel\\Bundle\\Bundle::getContainerExtension()\" might add \"?ExtensionInterface\" as a native return type declaration in the future. Do the same in child class \"Webkul\\UVDesk\\AutomationBundle\\UVDeskAutomationBundle\" now to avoid errors or add an explicit @return annotation to suppress this message. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/vendor/symfony/error-handler/DebugClassLoader.php:331)"} []
      [2023-12-12T14:47:44.440788+01:00] deprecation.INFO: User Deprecated: Method "Symfony\Component\HttpKernel\Bundle\Bundle::getContainerExtension()" might add "?ExtensionInterface" as a native return type declaration in the future. Do the same in child class "Webkul\UVDesk\ExtensionFrameworkBundle\UVDeskExtensionFrameworkBundle" now to avoid errors or add an explicit @return annotation to suppress this message. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Method \"Symfony\\Component\\HttpKernel\\Bundle\\Bundle::getContainerExtension()\" might add \"?ExtensionInterface\" as a native return type declaration in the future. Do the same in child class \"Webkul\\UVDesk\\ExtensionFrameworkBundle\\UVDeskExtensionFrameworkBundle\" now to avoid errors or add an explicit @return annotation to suppress this message. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/vendor/symfony/error-handler/DebugClassLoader.php:331)"} []
      [2023-12-12T14:47:44.440807+01:00] deprecation.INFO: User Deprecated: Method "Symfony\Component\HttpKernel\Bundle\Bundle::getContainerExtension()" might add "?ExtensionInterface" as a native return type declaration in the future. Do the same in child class "Webkul\UVDesk\MailboxBundle\UVDeskMailboxBundle" now to avoid errors or add an explicit @return annotation to suppress this message. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Method \"Symfony\\Component\\HttpKernel\\Bundle\\Bundle::getContainerExtension()\" might add \"?ExtensionInterface\" as a native return type declaration in the future. Do the same in child class \"Webkul\\UVDesk\\MailboxBundle\\UVDeskMailboxBundle\" now to avoid errors or add an explicit @return annotation to suppress this message. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/vendor/symfony/error-handler/DebugClassLoader.php:331)"} []
      [2023-12-12T14:47:44.440831+01:00] deprecation.INFO: User Deprecated: Method "Symfony\Component\HttpKernel\Bundle\Bundle::getContainerExtension()" might add "?ExtensionInterface" as a native return type declaration in the future. Do the same in child class "Webkul\UVDesk\SupportCenterBundle\UVDeskSupportCenterBundle" now to avoid errors or add an explicit @return annotation to suppress this message. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Method \"Symfony\\Component\\HttpKernel\\Bundle\\Bundle::getContainerExtension()\" might add \"?ExtensionInterface\" as a native return type declaration in the future. Do the same in child class \"Webkul\\UVDesk\\SupportCenterBundle\\UVDeskSupportCenterBundle\" now to avoid errors or add an explicit @return annotation to suppress this message. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/vendor/symfony/error-handler/DebugClassLoader.php:331)"} []
      [2023-12-12T14:47:44.440847+01:00] deprecation.INFO: User Deprecated: Method "Symfony\Component\HttpKernel\Bundle\Bundle::getContainerExtension()" might add "?ExtensionInterface" as a native return type declaration in the future. Do the same in child class "Webkul\UVDesk\ApiBundle\UVDeskApiBundle" now to avoid errors or add an explicit @return annotation to suppress this message. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Method \"Symfony\\Component\\HttpKernel\\Bundle\\Bundle::getContainerExtension()\" might add \"?ExtensionInterface\" as a native return type declaration in the future. Do the same in child class \"Webkul\\UVDesk\\ApiBundle\\UVDeskApiBundle\" now to avoid errors or add an explicit @return annotation to suppress this message. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/vendor/symfony/error-handler/DebugClassLoader.php:331)"} []
      [2023-12-12T14:47:44.440861+01:00] deprecation.INFO: User Deprecated: Since symfony/security-bundle 5.3: The ".container.private.security.password_encoder" service is deprecated, use "security.user_password_hasher" instead. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Since symfony/security-bundle 5.3: The \".container.private.security.password_encoder\" service is deprecated, use \"security.user_password_hasher\" instead. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/var/cache/dev/ContainerUcWwxIl/get_Container_Private_Security_PasswordEncoderService.php:22)"} []
      [2023-12-12T14:47:44.440876+01:00] deprecation.INFO: User Deprecated: Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Encoder\UserPasswordEncoder" class is deprecated, use "Symfony\Component\PasswordHasher\Hasher\UserPasswordHasher" instead. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Since symfony/security-core 5.3: The \"Symfony\\Component\\Security\\Core\\Encoder\\UserPasswordEncoder\" class is deprecated, use \"Symfony\\Component\\PasswordHasher\\Hasher\\UserPasswordHasher\" instead. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/vendor/symfony/security-core/Encoder/UserPasswordEncoder.php:19)"} []
      [2023-12-12T14:47:44.440889+01:00] deprecation.INFO: User Deprecated: Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Encoder\UserPasswordEncoderInterface" interface is deprecated, use "Symfony\Component\PasswordHasher\Hasher\UserPasswordHasherInterface" instead. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Since symfony/security-core 5.3: The \"Symfony\\Component\\Security\\Core\\Encoder\\UserPasswordEncoderInterface\" interface is deprecated, use \"Symfony\\Component\\PasswordHasher\\Hasher\\UserPasswordHasherInterface\" instead. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/vendor/symfony/security-core/Encoder/UserPasswordEncoderInterface.php:17)"} []
      [2023-12-12T14:47:44.440903+01:00] deprecation.INFO: User Deprecated: Since symfony/security-bundle 5.3: The "security.encoder_factory.generic" service is deprecated, use "security.password_hasher_factory" instead. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Since symfony/security-bundle 5.3: The \"security.encoder_factory.generic\" service is deprecated, use \"security.password_hasher_factory\" instead. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/var/cache/dev/ContainerUcWwxIl/getSecurity_EncoderFactory_GenericService.php:22)"} []
      [2023-12-12T14:47:44.440920+01:00] deprecation.INFO: User Deprecated: Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactory" class is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactory" instead. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Since symfony/security-core 5.3: The \"Symfony\\Component\\Security\\Core\\Encoder\\EncoderFactory\" class is deprecated, use \"Symfony\\Component\\PasswordHasher\\Hasher\\PasswordHasherFactory\" instead. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/vendor/symfony/security-core/Encoder/EncoderFactory.php:20)"} []
      [2023-12-12T14:47:44.440934+01:00] deprecation.INFO: User Deprecated: Since symfony/security-core 5.3: The "Symfony\Component\Security\Core\Encoder\EncoderFactoryInterface" class is deprecated, use "Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactoryInterface" instead. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Since symfony/security-core 5.3: The \"Symfony\\Component\\Security\\Core\\Encoder\\EncoderFactoryInterface\" class is deprecated, use \"Symfony\\Component\\PasswordHasher\\Hasher\\PasswordHasherFactoryInterface\" instead. at /home/helpdesk-support/htdocs/helpdesk.example.com/helpdesk-project/vendor/symfony/security-core/Encoder/EncoderFactoryInterface.php:17)"} []
      

      Urls and usernames have been masked for protection.

      These are only deprecation warnings. Should they cause fatal errors in php operations?

      posted in Technical Help
      E
      escozul
    • RE: Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      @peopleinside Hello,

      I was forced to complete the setup using terminal when I had that issue with the vhost. Once I corrected it the uvdesk started working properly but I had skipped the wizard. However, php mailparse is installed (you have to install it even if you try to complete the installation using terminal. You actually get prompted to install maiplarse during the composer installation phase.)
      The email is the correct email and the error appears AFTER the php command opens the first email. That first email is then marked as read. If there are more than one emails in the inbox, I get a 1 of 2 emails processing, the first one is marked as read but still get the error and the process quits.

      I still wonder what that API https://uvdesk.example.com/mailbox/listener part of the echo is...

      posted in Technical Help
      E
      escozul
    • RE: Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      @peopleinside Thanks for the reply.

      Also, I appreciate the email masking, but I was already using invalid emails and domains 🙂

      my server uses php 8.1 as default but supports 8.2 and 8.3.
      The site is set to 8.3
      When running terminal I use 8.1 (php defaults to 8.1)
      but I tried forcing to use 8.3 by modifying the php command to php8.3 bin/console uvdesk:refresh-mailbox support_mailbox@domain.ext but I got the same error.

      posted in Technical Help
      E
      escozul
    • Warning: Trying to access array offset on value of type null when trying to refresh a mailbox

      Hello,

      I followed this guide to setup my mailbox: https://www.uvdesk.com/en/blog/setup-gmail-mailbox-uvdesk-open-source-helpdesk/ but when I try to run the php command that should refresh the mailbox and create the tickets I get the following output:

      php bin/console uvdesk:refresh-mailbox support_mailbox@domain.ext
      
      # Retrieving mailbox configuration details for support_mailbox@domain.ext:
      
        - Establishing connection with mailbox
        - Fetching all emails since 09 December 2023
        - Found a total of 1 emails in mailbox since 09 December 2023
      
        # Processing all found emails iteratively:
      
          API https://uvdesk.example.com/mailbox/listener
      
          - Processing email 1 of 1:
        An unexpected error occurred: Warning: Trying to access array offset on value of type null
      

      It seems that it connects to the mailbox just fine, retrieves the emails just fine but has trouble creating the tickets.
      Yes the specified mailbox contains just one email which is a test email. It should be imported and made into a ticket.
      So the 1 of 1 part is correct.
      I sent a second one, and same deal. processint email 1 of 2 and then ... error.

      The emails in the mailbox are marked as "read" when I run the php command. Which means it's not a credentials issue.

      I see that API https://uvdesk.example.com/mailbox/listener
      What is this? Should I have enabled the API so that uvdesk can process icomming emails?
      Something else?

      posted in Technical Help
      E
      escozul
    • RE: Nginx server 404 error after installation

      Hello,

      Thank you for replying.

      I was able to resolve the issue.
      It was as simple as setting the root of my project to include /public and not having to run it on a folder.
      In reality it was an issue with my NGINX vhost. I had to include a root for /public. Either that or setting /public to root. I chose the latter and left the vhost intact.

      I too feel sour about how the uvdesk team are treating us.
      Seeing the lack of support for simple and basic issues, makes me not want to suggest this piece of software to my customers. Given the fact that there are quite a few self-hosted, open-source helpdesk solutions out there, I plan to do my research and end up with the most reliable team.UVdesk is not it!

      posted in Technical Help
      E
      escozul
    • Nginx server 404 error after installation

      I tried to install the uvdesk using the instructions located here: https://github.com/uvdesk/community-skeleton.

      The package was downloaded and installed on my system along with all the dependencies and required packages. I faced no issue during the installation and it seemed to complete without error. I have a full capture of the log of the installation if you require it to troubleshoot.

      I have not setup the database yet so I navigated to my installation page located at https://www.example.com/public/index.php and as soon as I pressed the "Lets Begin" button I was taken to an error screen with the error "Unable to locate the path on the server" 4 times.

      The server runs Nginx and supports php 8.1.
      It also supports previous versions of php and up to 8.3. So if the problem is my php version, I can change it.
      ------Update-----
      I was able to proceed with the initial configuration using ssh. I run the command: php bin/console uvdesk:configure-helpdesk and I was able to connect to the database and create an admin user.

      Now, when I try to get to https://www.example.com/public/index.php I get a 404 error from NGINX.

      It seems to me that this is the same issue, and that it's not related to PHP. When I go to my error logs on the server, the php error log is completely empty and the NGINX access and error logs are full of 404 errors.

      I believe it's something to do with my NGINX vhost file but I really don't know where to begin.

      Do you have any tips about what directives should be included in the NGINX vhosts file? Maybe If I copied the vhosts file and shared it with you, you could spot the issue?

      posted in Technical Help
      E
      escozul