<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Migrating Incredible PBX 2022 to a PUBLIC-Facing Cloud PBX	</title>
	<atom:link href="https://nerdvittles.com/migrating-incredible-pbx-2022-to-a-public-facing-cloud-pbx/feed/" rel="self" type="application/rss+xml" />
	<link>https://nerdvittles.com/migrating-incredible-pbx-2022-to-a-public-facing-cloud-pbx/</link>
	<description>Ward Mundy&#039;s Technobabblelog</description>
	<lastBuildDate>Sat, 15 Oct 2022 23:39:12 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Eric Einstein		</title>
		<link>https://nerdvittles.com/migrating-incredible-pbx-2022-to-a-public-facing-cloud-pbx/comment-page-1/#comment-180513</link>

		<dc:creator><![CDATA[Eric Einstein]]></dc:creator>
		<pubDate>Sat, 15 Oct 2022 23:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=35304#comment-180513</guid>

					<description><![CDATA[Curious how to allow ssl web access only and restrict http. 

Getting the below timeout error when generating a Let&#039;s Encrypt certificate using the GUI:

lechecker: Pest_Curl_Exec - Operation timed out after 30001 milliseconds with 0 bytes received
The LetsEncrypt servers only send challenge queries to port 80. Certificate requests will fail if public access via port 80 is not available.

&lt;i&gt;[WM: I suspect the firewall is blocking access for the update. Let me suggest posting this on &lt;a href=&quot;https://www.voip-info.org/forum/&quot; target=&quot;_blank&quot; rel=&quot;noopener nofollow ugc&quot;&gt;our forum&lt;/a&gt; so everyone can participate in the discussion.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>Curious how to allow ssl web access only and restrict http. </p>
<p>Getting the below timeout error when generating a Let&#8217;s Encrypt certificate using the GUI:</p>
<p>lechecker: Pest_Curl_Exec &#8211; Operation timed out after 30001 milliseconds with 0 bytes received<br />
The LetsEncrypt servers only send challenge queries to port 80. Certificate requests will fail if public access via port 80 is not available.</p>
<p><i>[WM: I suspect the firewall is blocking access for the update. Let me suggest posting this on <a href="https://www.voip-info.org/forum/" target="_blank" rel="noopener nofollow ugc">our forum</a> so everyone can participate in the discussion.]</i></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Eric Einstein		</title>
		<link>https://nerdvittles.com/migrating-incredible-pbx-2022-to-a-public-facing-cloud-pbx/comment-page-1/#comment-180511</link>

		<dc:creator><![CDATA[Eric Einstein]]></dc:creator>
		<pubDate>Fri, 14 Oct 2022 14:33:55 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=35304#comment-180511</guid>

					<description><![CDATA[How would this work for whitelisting DDNS instead of IP addresses? All of my access to the GUI is from a few dynamically assigned addresses, but they all use dynamic DNS.

&lt;i&gt;[WM: That&#039;s what the &lt;strong&gt;add-fqdn&lt;/strong&gt; script was designed for.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>How would this work for whitelisting DDNS instead of IP addresses? All of my access to the GUI is from a few dynamically assigned addresses, but they all use dynamic DNS.</p>
<p><i>[WM: That&#8217;s what the <strong>add-fqdn</strong> script was designed for.]</i></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: David		</title>
		<link>https://nerdvittles.com/migrating-incredible-pbx-2022-to-a-public-facing-cloud-pbx/comment-page-1/#comment-180331</link>

		<dc:creator><![CDATA[David]]></dc:creator>
		<pubDate>Thu, 11 Aug 2022 21:08:36 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=35304#comment-180331</guid>

					<description><![CDATA[A long time fan of nerdvittles, first time commenting.

PBX server is well protected, but any decent way to protect IP phones, especially when need to reach the PBX switch outside the premise over the internet?

&lt;i&gt;[WM: Put the phone behind a hardware-based firewall.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>A long time fan of nerdvittles, first time commenting.</p>
<p>PBX server is well protected, but any decent way to protect IP phones, especially when need to reach the PBX switch outside the premise over the internet?</p>
<p><i>[WM: Put the phone behind a hardware-based firewall.]</i></p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
