Report post You have 30 minutes to complete this form before the CAPTCHA will expire. Security image * Required field JavaScript is required to view this page. Either you do not have JavaScript enabled in your web browser, you do not have cookies enabled in your web browser, or this website is misconfigured such that cookies do not save correctly. This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param="NextCloud"]299[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by 1123artc<br /><br /><comcode-quote param="184">Thanks for all the help - I've had it up and running well for a couple days. No problem with the public IP address changing but I'll keep an eye on it. I've seen a lot of talk about DuckDNS as well for dynamic DNS, which seems to be growing in popularity compared to NoIP. <br /><br />I just wound up forwarding both 80 and 443, but I also used the option with Let's Encrypted to redirect to HTTPS so I guess it should all go through 443. Thanks for noting that about connecting to my domain from within my network. I haven't had any problems yet, but I also use a VPN on my other devices so maybe that has some impact. <br /><br />For others who happen to come accros this, my setup is with Ubuntu Server 18.04, manually installed LAMP, a domain pointing to my router external IP address with Let's Encrypt redirected to always be HTTPS, and port forwarding in my router with both port 80 and port 443 pointing to my web server private IP address. Essentially followed the NOTS tutorial but hosting from a physical server at my home and port forwarding. <br /><br />Again, thanks for the help!<br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br /> Add: Add: Font Size Color [Font] Arial Courier Georgia Impact Times Trebuchet Verdana Tahoma Geneva Helvetica [Size] 0.8 1 1.5 2 2.5 3 4 [Color] Black Blue Gray Green Orange Purple Red White Yellow This is a reported post for a post in the topic [post param="NextCloud"]299[/post], by 1123artc [quote="184"] Thanks for all the help - I've had it up and running well for a couple days. No problem with the public IP address changing but I'll keep an eye on it. I've seen a lot of talk about DuckDNS as well for dynamic DNS, which seems to be growing in popularity compared to NoIP. I just wound up forwarding both 80 and 443, but I also used the option with Let's Encrypted to redirect to HTTPS so I guess it should all go through 443. Thanks for noting that about connecting to my domain from within my network. I haven't had any problems yet, but I also use a VPN on my other devices so maybe that has some impact. For others who happen to come accros this, my setup is with Ubuntu Server 18.04, manually installed LAMP, a domain pointing to my router external IP address with Let's Encrypt redirected to always be HTTPS, and port forwarding in my router with both port 80 and port 443 pointing to my web server private IP address. Essentially followed the NOTS tutorial but hosting from a physical server at my home and port forwarding. Again, thanks for the help! [/quote] //// PUT YOUR REPORT BELOW \\\\ Use of this website implies that you agree to the website rules and privacy policy.