Hey Everyone,

I'm rather new to osTicket, but I have an instance up and running in a VM under a Proxmox hypervisor. Everything has been going smoothly with the exception of email integration. The environment I'm working in has an odd ("bespoke" as I like to call it tongue-in-cheek) email server set up that has fused a locally hosted Outlook mail server with a cloud based one, but I doubt this is the current issue.

After following the guide for the OAuth2 plugin and entering the appropriate user credentials, I get this:

I'm almost certain osTicket is missing something, but I cannot quite determine what it is. Any thoughts or suggestions?

    hobbsmc

    If using a supported webserver (Apache, IIS, LiteSpeed) you simply do not have URL rewriting installed/enabled on your webserver. If you are using NGINX then you need to go online and find a working recipe that contains the API endpoints, apply it, restart NGINX, and retest.

    Cheers.

      Thank you very much! That seems to have made the plugin work correctly.

      I'm not sure if the etiquette on this forum is to start a new thread for a new topic, but I've immediately hit another roadblock that may be a bit of a bigger issue. Some details were mentioned previously, so I'll continue here unless told otherwise:

      As mentioned in the prior post, the mail server situation here is... unique. We effectively have two domains, and when I ping the mail server's IP address, I receive three different hostnames. I have tried every combination of hostname, domain (there are two), protocol and port (albeit, only the typical ports, all of which are open on both the osTicket server and the mail server). The errors I get are always timeout errors... yet I can ping the mail server from the osTicket sever with hardly any latency. I'm using the Oauth2 plugin, as mentioned previously. Any thoughts or ideas would be greatly, greatly appreciated.

      Update: It is specifically enabling email fetching that results in timeout errors. Everything else saves successfully and produces no errors.

      That was premature. I tested the outgoing email, and an error was produced:

      Fatal error: Uncaught Laminas\Mail\Protocol\Exception\RuntimeException: Could not read from ..com in /var/www/html/osTicket/include/laminas-mail/src/Protocol/AbstractProtocol.php:314 Stack trace: #0 /var/www/html/osTicket/include/laminas-mail/src/Protocol/AbstractProtocol.php(342): Laminas\Mail\Protocol\AbstractProtocol->receive() #1 /var/www/html/osTicket/include/laminas-mail/src/Protocol/Smtp.php(466): Laminas\Mail\Protocol\AbstractProtocol->expect() #2 /var/www/html/osTicket/include/laminas-mail/src/Protocol/Smtp.php(502): Laminas\Mail\Protocol\Smtp->quit() #3 /var/www/html/osTicket/include/laminas-mail/src/Protocol/Smtp.php(492): Laminas\Mail\Protocol\Smtp->_disconnect() #4 /var/www/html/osTicket/include/laminas-mail/src/Transport/Smtp.php(171): Laminas\Mail\Protocol\Smtp->disconnect() #5 [internal function]: Laminas\Mail\Transport\Smtp->__destruct() #6 {main} thrown in /var/www/html/osTicket/include/laminas-mail/src/Protocol/AbstractProtocol.php on line 314

      I placed the asterisks in the domain for privacy.

        hobbsmc

        It simply cannot read from the host/port. Make sure you are using the right host and port.

        Cheers.

          Write a Reply...