<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ChatGPT Access in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/562693#M113969</link>
    <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp; We have configured the new domain to be dropped as Sinkhole. So may be that could be the cause.&lt;/P&gt;
&lt;P&gt;May i know which is the new domain so that will add that in the DNS exemption.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Sanjay S&lt;/P&gt;</description>
    <pubDate>Mon, 23 Oct 2023 04:45:49 GMT</pubDate>
    <dc:creator>Sanjay_Ramaiah</dc:creator>
    <dc:date>2023-10-23T04:45:49Z</dc:date>
    <item>
      <title>ChatGPT Access</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/562566#M113950</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;Users are trying to access ChatGPT and getting error, but we have allowed teh ChatGPT APP-ID and still the same. Not even seeing any error at all. What is the best way to fix it?&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Sanjay S&lt;/P&gt;</description>
      <pubDate>Fri, 20 Oct 2023 12:49:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/562566#M113950</guid>
      <dc:creator>Sanjay_Ramaiah</dc:creator>
      <dc:date>2023-10-20T12:49:23Z</dc:date>
    </item>
    <item>
      <title>Re: ChatGPT Access</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/562581#M113953</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/249853"&gt;@Sanjay_Ramaiah&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Ensure that you've enabled some form of logging for denied interzone traffic. You can do this by enabling logging on the interzone-default entry, or building an entry yourself and setting it to deny anything not already caught by your rulebase. That'll account for any traffic that's getting dropped due to something missing in your rulebase.&lt;/P&gt;
&lt;P&gt;Outside of that, ensure that you review all of your logs as well. OpenAI recently added a new domain that is/was still classified as newly-registered-domain, so you could be preventing access to that domain depending on how you've configured your URL profiles and your anti-spyware profile and verify how your DNS Policy options look like for the same newly registered domains entry.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Oct 2023 13:40:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/562581#M113953</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2023-10-20T13:40:04Z</dc:date>
    </item>
    <item>
      <title>Re: ChatGPT Access</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/562693#M113969</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp; We have configured the new domain to be dropped as Sinkhole. So may be that could be the cause.&lt;/P&gt;
&lt;P&gt;May i know which is the new domain so that will add that in the DNS exemption.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Sanjay S&lt;/P&gt;</description>
      <pubDate>Mon, 23 Oct 2023 04:45:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/562693#M113969</guid>
      <dc:creator>Sanjay_Ramaiah</dc:creator>
      <dc:date>2023-10-23T04:45:49Z</dc:date>
    </item>
    <item>
      <title>Re: ChatGPT Access</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/562755#M113987</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/249853"&gt;@Sanjay_Ramaiah&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;cdn.oaistatic.com is the last one that was added.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Oct 2023 13:30:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/562755#M113987</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2023-10-23T13:30:30Z</dc:date>
    </item>
    <item>
      <title>Re: ChatGPT Access</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/565097#M114298</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;Thank you for the help. Looks like Palo public IPs are being blocked by ChatGPT and hence it was not working. When we did traffic steering it worked. Looks like Palo already raised ticket with ChatGPT and awaiting response on whitelisting Palo ranges.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 05:26:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/chatgpt-access/m-p/565097#M114298</guid>
      <dc:creator>Sanjay_Ramaiah</dc:creator>
      <dc:date>2023-11-10T05:26:14Z</dc:date>
    </item>
  </channel>
</rss>

