<?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: Nest Wifi Pro Port Forwarding Issue Docker in Nest Wifi</title>
    <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/423411#M43925</link>
    <description>&lt;P&gt;Hello Abigail! I submitted one to Google, received one suggestion that didn't work and nothing further after multiple inquiries. I've ditched the nest wifi 6 for nighthawk mesh wifi 6 and it's been so much better. I'm sincerely disappointed in Google. They just came out with this less than a year ago and you cannot even port forward to IPs you want.&lt;/P&gt;</description>
    <pubDate>Wed, 24 May 2023 22:47:10 GMT</pubDate>
    <dc:creator>PoeticArcher</dc:creator>
    <dc:date>2023-05-24T22:47:10Z</dc:date>
    <item>
      <title>Nest Wifi Pro Port Forwarding Issue Docker</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/382592#M40983</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have an unraid server with some docker containers. It has a static up of 192.168.86.50. There is an app running on this server in Docker in Bridge network on port 1443. So, in the Google Home app I forwarded port 443 to the unraid server, to 1443. Everything works fine. In port management in Google Home it shows the device with an IP address of 192.168.86.50 and we are good. Next I spun up a DNS server on this unraid machine and gave it br0 network type so I could give it an IP address of 192.168.86.51. I can ping both 192.168.86.50 and 192.168.86.51 from a PC on LAN no problem, however, now all of a sudden, in my Google Home app it changes the IP of the port forward to 192.168.86.51 and my app no longer works on WAN as it did before. Adding this new app with a static IP messes with Google Home's port forwarding. I want it forward 443 to 192.168.86.50:1443 not&amp;nbsp;192.168.86.51:1443. How can I solve this?&lt;BR /&gt;&lt;BR /&gt;Thank you for your help!&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2023 00:04:55 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/382592#M40983</guid>
      <dc:creator>PoeticArcher</dc:creator>
      <dc:date>2023-03-21T00:04:55Z</dc:date>
    </item>
    <item>
      <title>Re: Nest Wifi Pro Port Forwarding Issue Docker</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/385698#M41276</link>
      <description>&lt;P&gt;Hey PoeticArcher,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for posting and apologies for the late reply. I appreciate your explanation regarding your issue. I’d like to get more details. Could you send a screenshot of what you input in your Google Home app for port forwarding? I’ll wait for your update.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Abi&lt;/P&gt;</description>
      <pubDate>Sun, 26 Mar 2023 03:25:16 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/385698#M41276</guid>
      <dc:creator>AbigailF</dc:creator>
      <dc:date>2023-03-26T03:25:16Z</dc:date>
    </item>
    <item>
      <title>Re: Nest Wifi Pro Port Forwarding Issue Docker</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/386429#M41425</link>
      <description>&lt;P&gt;Hi Abi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your assistance! Here's a screenshot of the port forwarding page. To note, I had forwarded it when it was displaying .50 but after turning on my dns server it changed.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20230327_104911_Home.jpg" style="width: 466px;"&gt;&lt;img src="https://www.googlenestcommunity.com/t5/image/serverpage/image-id/22737iE2DFF99C0F483C3F/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot_20230327_104911_Home.jpg" alt="Screenshot_20230327_104911_Home.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 17:52:21 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/386429#M41425</guid>
      <dc:creator>PoeticArcher</dc:creator>
      <dc:date>2023-03-27T17:52:21Z</dc:date>
    </item>
    <item>
      <title>Re: Nest Wifi Pro Port Forwarding Issue Docker</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/419667#M43600</link>
      <description>&lt;P&gt;Hi PoeticArcher,&lt;BR /&gt;&lt;BR /&gt;Thanks for the update and my apologies for the late reply. I'm sorry to hear that you're still having an issue with your Nest Wifi Pro. We'd like to take a deeper look into this — could you fill out this &lt;A href="https://goo.gle/3BICUaB" target="_blank"&gt;form&lt;/A&gt; and let us know once you're done?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Abi&lt;/P&gt;</description>
      <pubDate>Wed, 17 May 2023 05:03:32 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/419667#M43600</guid>
      <dc:creator>AbigailF</dc:creator>
      <dc:date>2023-05-17T05:03:32Z</dc:date>
    </item>
    <item>
      <title>Re: Nest Wifi Pro Port Forwarding Issue Docker</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/421512#M43748</link>
      <description>&lt;P&gt;Hey there,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Checking back in — have you had the chance to fill out the form?&lt;BR /&gt;&lt;BR /&gt;Best,&amp;nbsp;&lt;BR /&gt;Abi&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 02:29:13 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/421512#M43748</guid>
      <dc:creator>AbigailF</dc:creator>
      <dc:date>2023-05-21T02:29:13Z</dc:date>
    </item>
    <item>
      <title>Re: Nest Wifi Pro Port Forwarding Issue Docker</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/423406#M43922</link>
      <description>&lt;P&gt;Hello PoeticArcher,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I wanted to follow up and see if you are still in need of any help. If so, please fill out the form so we can help you further.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Abi&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 22:40:06 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/423406#M43922</guid>
      <dc:creator>AbigailF</dc:creator>
      <dc:date>2023-05-24T22:40:06Z</dc:date>
    </item>
    <item>
      <title>Re: Nest Wifi Pro Port Forwarding Issue Docker</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/423411#M43925</link>
      <description>&lt;P&gt;Hello Abigail! I submitted one to Google, received one suggestion that didn't work and nothing further after multiple inquiries. I've ditched the nest wifi 6 for nighthawk mesh wifi 6 and it's been so much better. I'm sincerely disappointed in Google. They just came out with this less than a year ago and you cannot even port forward to IPs you want.&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 22:47:10 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-Wifi-Pro-Port-Forwarding-Issue-Docker/m-p/423411#M43925</guid>
      <dc:creator>PoeticArcher</dc:creator>
      <dc:date>2023-05-24T22:47:10Z</dc:date>
    </item>
  </channel>
</rss>

