Same issue here, having checked IMAP using other accounts and on different clients, this looks to be a Microsoft issue, although no acknowledgement as yet.

Looks to have started after approx. 19:00 (GMT) on 27th December.

    I'm having the exact same issue as well, the oauth2 process works, tokens get refreshed, but no emails are being fetched anymore and the error "cannot select INBOX, is this a valid transport?" pops up every time when trying to save.
    I was originally using version 0.2 of the oauth2 plugin, but updating it didn't help.
    I can also confirm that the issue started about 2 days ago, with no issues for months before that.

    cubanp3te

    Why do you believe that? That really gives me a bit of hope since I was about to lose it....

    Found more issue I think might be related:

    Link (https://sugarclub[dot]sugarcrm[dot]com/explore/help-forums/enterprise-professional/f/enterprise-professional-questions/6111/group-email-account-not-archiving-from-mailbox)

    Another (https://pullanswer[dot]com/questions/collector-not-working-imap-oauth-tag2-bad-user-is-authenticated-but-not-connected)

    And another

    It looks like an IPv6 issue though, please follow this guide and test it:

    https://itsfoss[dot]com/disable-ipv6-ubuntu-linux/

    Looks like it's working when I disable IPv6. Can't explain it though...

      Rickymundo I was having the same issue that has been listed here and several other times.

      I had tried ALL other fixes supplied and this was the only one that worked and I can confirm it worked.

      Microsoft Support had confirmed to me that nothing had changed on the 27th December (mine stopped working then too). I will let them know this knowledge so they can investigate.

      • az68 replied to this.

        olimartin
        Hi,
        Do you have any idea why it worked before 27 ? And what it the role of IPV6 ?

        I have the same issue, but i don't have a vps or private server, I don't know if I can disable IPV6 to my host.

          Hi Kevin,
          I have the same error with os ticket. The following links are shown:
          https://forum.osticket.com/d/101803-the-requested-url-apiauthoauth2-was-not-found-on-this-server/7
          After adding the LDP setting, going to add credentials, and then adding admin credentials, I get a time-out error on my direct URL.
          I am using centos 8 and osTicket 1.17.
          am added the rewrite permission also on the server.
          can you please help me...

            Hi,
            I run in to very similar if not same issue. After plugin installation I got prompt to log in to O365, but ended with "File not found" after redirect. I removed plugin, added it again and now I stuck with "LOADING.." after I submit settings for ldP config. Tried different web browsers, incognito, same result.
            Removed IPv6 already, didn't helped. Like some kind of cache or something on server??
            Any help on this ?

              MarcinZ Delete the email and re-add it and reconfigure it.

              bhushan timeout is indicative of deeper issues. You need to check your logs for any related errors. You can also try deleting the email and reading it. Also, you need to be running v1.17.2 and the latest build of the OAuth2 plugin.

              Cheers.

                MarcinZ

                URL Rewriting isn’t enabled or configured properly. You need to research older discussions on this on how to get it working with NGINX. A community member posted their working config in an older thread. I don’t remember which discussion it was so you’ll have to do some searching.

                Cheers.

                  Is there any update on the "cannot select INBOX, is this a valid transport?". My installation also stopt fetching mails on the 27-december. I have tried a couple of things (removed and added the email adresses in osTicket an removed and added the registration in the microsoft tenant), but nothing seems to have any effect. I can send email with the Microsoft 365 account, but i cant read the emails from the microsof365 accounts.

                  I can't disable ipv6 on the server because there a more sites on the same server witch need ipv6. For now i have a little workaround to forward the mails to a external mailbox witch a can read with IMAP.

                  Hi Kevin,
                  I reset the my web server, and now it is going to authenticate and redirect to login Microsoft after fillup the Microsoft plugin config, I am authenticated with the Azure admin, it time out when redirecting the URL on my server.

                    KevinTheJedi
                    Thanks Kevin for your help! It did help. I have finished mail configuration. For those who struggle with NGINX rewrite config, you need to add auth in api rewrite rule. Details here
                    https://github.com/osTicket/osTicket/issues/6293#issuecomment-1315838614

                    But still I can't fetch email's from O365. Diagnostic is able to sent, but emails on INBOX are not processed. Any hint where to start to look? No error in OSTicket log (in debug mode). IPv6 disabled.
                    OK. I fixed the problem. In my case bumpy update of our Ubuntu deleted crontab. So task cron.php was not scheduled.

                    THX,
                    -Marcin

                    az68 Honestly - no idea as to why it would suddenly stop supporting IPv6 - perhaps this is something the osTicket devs can look into with Microsoft. From a quick search it seems that IPv6 and Exchange have never gotten on well.. but why it would stop working suddenly over Christmas is strange as my configuration with osTicket worked perfectly prior but it does show a suddent stop at 00:01 on the 27th December 2022.. which is why this issue isn't well documented on here yet.

                    What are you hosting on? I may be able to help you disable it. For osTicket and it's various plugins etc. I would recommend wither a VPS or using their hosted model as I have used web-hosting services for it before and had constant issues.. AWS Lightsail is a very cheap way of doing it yourself.