<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title><![CDATA[Cloud Gateways | Topics | Ubiquiti Community]]></title>
        <description><![CDATA[Cloud Gateways | Topics | Ubiquiti Community]]></description>
        <link>https://community.ui.com</link>
        <image>
            <url>https://community.ui.com/images/og-image.jpg</url>
            <title>Cloud Gateways | Topics | Ubiquiti Community</title>
            <link>https://community.ui.com</link>
        </image>
        <generator>Ubiquiti Community</generator>
        <lastBuildDate>Wed, 30 Sep 2026 21:45:56 GMT</lastBuildDate>
        <atom:link href="https://community.ui.com/rss/topics/unifi-cloud-gateway" rel="self" type="application/rss+xml"/>
        <pubDate>Wed, 30 Sep 2026 21:45:56 GMT</pubDate>
        <copyright><![CDATA[© 2026 Ubiquiti Inc. All rights reserved.]]></copyright>
        <item>
            <title><![CDATA[USW Pro Max 24 update failed.]]></title>
            <description><![CDATA[<p>New to UniFi, but I setup a Cloud Gateway Fiber (AT&amp;T Fiber) and a USW Pro Max 24 along with two U7 Pros.  Everything has adopted and is functioning well, but updates have not been working?  The Cloud Gateway Fiber update finally installed last night, but the USW Prox Max 24 update fails and I can't seem to find much detail as to why?</p><p>The update is from 7.0.21 to 7.1.26 with just two notifications of "update failed."  Any ideas?</p>]]></description>
            <link>https://community.ui.com/questions/USW-Pro-Max-24-update-failed/b1c0c00f-2bcc-492f-9ca1-66f5adf2c351</link>
            <guid isPermaLink="false">b1c0c00f-2bcc-492f-9ca1-66f5adf2c351</guid>
            <category><![CDATA[wifiman]]></category>
            <category><![CDATA[unifi-network]]></category>
            <category><![CDATA[new-to-unifi]]></category>
            <category><![CDATA[unifi-cloud-gateway]]></category>
            <dc:creator><![CDATA[danieldgarrett]]></dc:creator>
            <pubDate>Tue, 15 Apr 2025 13:18:26 GMT</pubDate>
        </item>
        <item>
            <title><![CDATA[Site-to-site (Site-magic) stuck on connecting - Wireguard port blocked?]]></title>
            <description><![CDATA[<p>I have 2 sites (UCG - Ultra and UCG-Max) both on the latest official releases where attempting to create a site magic site-to-site VPN results in a 'Connecting' state and never comes up.</p><p>I did some troubleshooting and did notice something peculiar - when I manually create a Wireguard VPN server on my UCG-Max the assigned port is not open. The connectivity is allowed through the firewall and I can create an OpenVPN server on the same site which works fine.</p><p>It looks like the wireguard server is not listening to connections on the UCG-Max and I believe site magic uses Wireguard, hence I suspect that is the cause site magic is unsuccessful.</p><p>Any suggestions on a remedy? I have previously attempted the below:</p><ul><li>Removed any custom firewall rules, NAT, static routes, port forwarding etc. and attempted to delete and create</li><li>Rebooted the UCG-Max and UCG-Ultra</li><li>Tried different port numbers for wireguard</li></ul>]]></description>
            <link>https://community.ui.com/questions/Site-to-site-Site-magic-stuck-on-connecting-Wireguard-port-blocked/308f78fd-9eea-4b72-9d79-42d8186ede5b</link>
            <guid isPermaLink="false">308f78fd-9eea-4b72-9d79-42d8186ede5b</guid>
            <category><![CDATA[unifi-network]]></category>
            <category><![CDATA[unifi]]></category>
            <category><![CDATA[site-manager]]></category>
            <category><![CDATA[unifi-cloud-gateway]]></category>
            <category><![CDATA[unifi-gateway-cloudkey]]></category>
            <category><![CDATA[unifi-routing-switching]]></category>
            <dc:creator><![CDATA[kashefcom]]></dc:creator>
            <pubDate>Mon, 14 Apr 2025 07:50:56 GMT</pubDate>
        </item>
        <item>
            <title><![CDATA[What am I missing: Moving pfSense into Aggregation Switch]]></title>
            <description><![CDATA[<p>I've built out my home network over time and only recently started replacing old TPLink gear with Ubiquiti. I ran into a snag when trying to move my pfSense Protecli router and was hoping for some feedback on what I did wrong or don't understand.</p><p><br></p><p>I have comcast internet coming into the pfSense and the LAN from that going into an RJ45 port of a USW-Pro-24 switch. For numerous home lab reasons I have DHCP handled by the pfSense router, but DNS handled by pihole and Windows Server forwarding for the domain.&nbsp;</p><p><br></p><p>Once I moved to Ubiquiti access points I added a USW-Pro-24-POE to the mix.&nbsp;</p><p><br></p><p>In an effort to add 10Gb connectivity to my network for a VMware vSAN cluster among other things I added the USW-Aggregation which I then connected the PoE and Pro-24 up to via SFP+ DAC.&nbsp;No issues. Works great. </p><p><br></p><p>A small TPLink switch was also connected to the aggregation switch via 10Gtek 1.25/2.5/5/10G-T SFP+ to RJ45 CAT.6a Copper Transceiver set to 1Gb and worked without issue.&nbsp;</p><p><br></p><p>My understanding was that my router should also be going through the aggregation switch rather than hanging off the side of one of the switches so I got another SFP+ to RJ45 transceiver to go about making this change.&nbsp;</p><p><br></p><p>I shut down the pfSense and connected it to the aggregation switch via transceiver setting the port to switching and 1Gbps FDX. I powered it on and switches in unifi just started disconnecting. The switches were dropping to their default IP of 192.168.1.20 because they couldn’t see the DHCP server which is coming from pfSense.&nbsp;</p><p>I tried restarting the aggregation and PoE switches but still didn’t get a correct IP.&nbsp;</p><p>I tried disconnecting DAC connections between aggregation and other switches and re-connecting but that did nothing.</p><p>The second I unplugged the transceiver in port 1 on the aggregation switch it showed the right IP on the front screen and everything popped up in the UI. That transceiver goes to one of the vSAN nodes which has never had an issue with connectivity and after putting everything back the way it was before has been fine since.&nbsp;</p><p><br></p><p>My question is, should the pfSense router be going into the aggregation switch and if so how do I go about getting it moved over without everything failing as it did?&nbsp;</p><p>Thanks</p><p><br></p>]]></description>
            <link>https://community.ui.com/questions/What-am-I-missing-Moving-pfSense-into-Aggregation-Switch/dc77c898-6217-49a6-92db-73ecac815600</link>
            <guid isPermaLink="false">dc77c898-6217-49a6-92db-73ecac815600</guid>
            <category><![CDATA[unifi]]></category>
            <category><![CDATA[unifi-routing-switching]]></category>
            <category><![CDATA[unifi-wireless]]></category>
            <category><![CDATA[unifi-cloud-gateway]]></category>
            <category><![CDATA[unifi-switching]]></category>
            <category><![CDATA[wifiman]]></category>
            <category><![CDATA[unifi-design-center]]></category>
            <dc:creator><![CDATA[minimoose]]></dc:creator>
            <pubDate>Sat, 08 Mar 2025 14:38:25 GMT</pubDate>
        </item>
    </channel>
</rss>