@aaronstuder said:

@JaredBusch Fixed! Sorry 😞

The permalink is in the timestamp.
0_1456860659059_upload-340da54e-03b8-46a5-b01e-5cb56a877190

@alex.olynyk said:

is there a way to notify a new user that we have created an OC account for them?

I don't believe so. I think that you will need to hand craft an email message for them.

@anonymous said:

Yes, you need to use a FQDN, then make sure port forwarding is working correctly 🙂

He does need the FQDN, but it sounds like he has that ready.

His problem is that the links the server gives out is not the FQDN.

That is handled in the config.

@alex.olynyk said:

The From To address field had to be a valid address. Its working now. Thanks everyone.

That was a restriction of your SMTP server, not ownCloud.

@alex.olynyk said:

@scottalanmiller It did. I am also looking at Smart Switches. Thank you.

It's a good middle ground price wise. We use all smart switches currently.

I missed a step. Forgot to type in IP of server. Sorry. Its working now. Thanks everyone.

I updated the firmware and its working now. Thank you to all who helped.

Thank you very much. Its working now.

@alex.olynyk said:

@scottalanmiller How to forward 8080 to 80 on the SW? In Firewall-Access Rules?

yes

@alex.olynyk said:

Server: CentOS 7

Database: SQLite

OC-Version:8.2.2

PHP-Version:5.4.16

I used the public server wizard on an NSA 2400 to create NAT policy and firewall rules for Own Cloud.
I setup httpd.conf to listen on port 8080
I added the public IP address of my SonicWALL with port 8080 to trusted domains.
When I go to http://Public_IP:8080 from outside the network I get page cant be found.
What am I missing? Please let me know if you need screenshots or log files.

The simplest answer is that ownCloud does not answer on http://Public_IP:8080. It answers on http://Public_IP:8080/owncloud

If that does not work, then you missed something in your firewall configs.

Of course this is all assuming that it works internally.

Very situational. We do Vultr often because it is so cost effective. We are deploying our newest on premises because of capacity reasons. All depends what you have, how you plan to use it, etc. All deployment options have a valid use case.