Now when I navigate to https://<servername>/nextcloud the web server is returning "Not Found The requested URL /nextcloud was not found on this server." It would appear Nextcloud is no longer available on the COS server.

Hey Nick,
thanks for your reply plus the tip. After backing up the COS server, I ran the command as requested.


I'm running a "yum check" and "yum clean" now

Uninstalled Nextcloud but still seeing Nextcloud via https:443

Hello Community,
I have migrated my ClearOS Nextcloud instance to a Turnkey Nextcloud some time ago (i.e. I've moved Nextcloud off the ClearOS server). I originally installed, then uninstalled Nextcloud via the ClearOS Marketplace.

There are still nextcloud directories in /var/clearos/ and /usr/share/. Are these safe to delete? Are there any other directories that also need removing? Is there anything that needs to be checked with Apache also?

I found this document very handy with finding the default admin password
ClearOS Documentation link here

the command I used (and it worked a treat)

Nick
thanks for the reply. Not sure what I'd do without you.

ls -al /mnt/cloudstore/owncloud/data/<username>/files
shows the same as
ls -al /var/clearos/owncloud/data/<username>/files

i touched a new file in /mnt/cloudstore/owncloud/data/<username>/files and it also appeared in /var/clearos/owncloud/data/<username>/files so the bind is correct

the /mnt/cloudstore is a 1Tb 2nd HDD attached to the VM and mounted with /etc/fstab


I'll dig a little deeper into this on the ownCloud forums and see what I can find

Error Uploading Files: 403 Forbibben

About a week ago I migrated my ClearOS 7.x Home firewall from a physical to a virtual server using Proxmox. Everything runs great, performance is also exceptional having given the VM 6Gb of Ram and 2 CPU cores.

COS 7 VM is running on a 128Gb (/dev/sda) disk with a 1Tb (/dev/sdb) disk dedicated for ownCloud storage. I've used the Storage Manager app to bind "/dev/sdb1/owncloud/data" to "/var/clearos/owncloud/data". The bulk 130Gb of my ownCloud local files have uploaded to the server (my user acct has unlimited ownCloud storage)

This was working perfectly until a couple of days ago. local file changes made are not being uploaded to the ownCloud server. <b> Server replied "403 Forbidden" to "PUT...</b> and a <b> Server replied "403 Forbidden" to "MOVE... </b> errors appearing in the local ownCloud client.

If I logon to the ownCloud server web interface and make any file changes there, these changes are being reflected on the local machines ownCloud dir. I'm also no longer able to manually upload files to the ownCloud Web Interface either.

I can roll back the VM to a previous version however don't want to have to reconfigure some of the server settings. the 2nd 1Tb disk is NOT in the Proxmox backup job. That's been omitted on purpose.

The central.ownCloud.org site forums have a few posts on this however I'd rather run this past the ClearOS forum.

Thanks for the clarification. When Clearcenter allow me the time, I'll update the HowTo, but note that your comment applies to which ever site hosts your domain. It is not restricted to Clearcenter hosting your domain.

FWIW your SPF record can also be simplified from:to:as hardingclan.org is assumed for the A and MX records. Your A record directly resolves to your IP and your MX record resolves to mail.hardingclan.org which resolves to hardingclan.org so there is no point in specifying the IP and the include just sends the SPF lookup in circles.

Thanks for the clarification. When Clearcenter allow me the time, I'll update the HowTo, but note that your comment applies to which ever site hosts your domain. It is not restricted to Clearcenter hosting your domain.

FWIW your SPF record can also be simplified from:to:as hardingclan.org is assumed for the A and MX records. Your A record directly resolves to your IP and your MX record resolves to mail.hardingclan.org which resolves to hardingclan.org so there is no point in specifying the IP and the include just sends the SPF lookup in circles.

Charles & Nick,
I've just been thru the process of creating a new domain and stepped thru the ClearOS Documentation HowTo for installing and creating a DKIM key. I also did EXACTLY as per the HowTo and reading your previous post Charles, I figured out where I also was going wrong.

In the HowTo it states

Now you need to update your DNS records. Open the file '/etc/opendkim/keys/mydomain.com/YYYYMM.txt'. In your DNS records, create a new TXT record with a subdomain as the first field in the file which you can just copy. In this case it is “YYYYMM._domainkey”. For TXT Data copy and paste everything between the first and last set of quotes, excluding the first and last quotes and removing the middle quotes and whitespace between them.

I didn't realize the "DNS records, create a new TXT record with a subdomain" were referencing the secure.clearcenter.com/portal/dns_txt.jsp" target="_blank">https://secure.clearcenter.com/portal/dns_txt.jsp where I'd set up my domain. I was thinking this was referencing somewhere on my COS server and was left scratching my head on this for almost a week!

Anyway, screenshots of the HowTo plus the ClearCenter DNS Config TXT tool

I repeated the Howto steps but added a new subdomain "202012._domainkey" using the DNS Config TXT tool on the secure.clearcenter.com/portal. and now I have a working openDKIM key.

I tested the SPF and DKIM key using https://www.mail-tester.com/spf-dkim-check
Everything now checks out and I'm confident I've got a valid SPF and DKIM record for my new Domain and emails should happily reach their destination... although this is still yet to be tested.

Charles & Nick,
I've just been thru the process of creating a new domain and stepped thru the ClearOS Documentation HowTo for installing and creating a DKIM key. I also did EXACTLY as per the HowTo and reading your previous post Charles, I figured out where I also was going wrong.

In the HowTo it states

Now you need to update your DNS records. Open the file '/etc/opendkim/keys/mydomain.com/YYYYMM.txt'. In your DNS records, create a new TXT record with a subdomain as the first field in the file which you can just copy. In this case it is “YYYYMM._domainkey”. For TXT Data copy and paste everything between the first and last set of quotes, excluding the first and last quotes and removing the middle quotes and whitespace between them.

I didn't realize the "DNS records, create a new TXT record with a subdomain" were referencing the secure.clearcenter.com/portal/dns_txt.jsp" target="_blank">https://secure.clearcenter.com/portal/dns_txt.jsp where I'd set up my domain. I was thinking this was referencing somewhere on my COS server and was left scratching my head on this for almost a week!

Anyway, screenshots of the HowTo plus the ClearCenter DNS Config TXT tool

I repeated the Howto steps but added a new subdomain "202012._domainkey" using the DNS Config TXT tool on the secure.clearcenter.com/portal. and now I have a working openDKIM key.

I tested the SPF and DKIM key using https://www.mail-tester.com/spf-dkim-check
Everything now checks out and I'm confident I've got a valid SPF and DKIM record for my new Domain and emails should happily reach their destination... although this is still yet to be tested.