INstall guide for a newbie

šŸš§ Installation
1

Hi all,

Iā€™m starting from scratch on a new installation: This is a manual installation vs a snap.

My Linux is better, but still ā€œBeginnerā€ - I can run most commends i need, the trouble i have is finding the files (And typoā€™s!).

It will be run from Ubuntu 16.04 LTS, with PhP 7, Apache, MySql\MariaDB, Which i am setting up now.

Does anyone have a simple\up-to date guide on how i can do this?

2

Try this one?

3

@JasonBayton - Thanks - It goes so well then i hit 2 problems -

1 - is NXDOMAIN looking up A record for ā€œcloud.domain.comā€ - This is an issue i hit all the timeā€¦ Iā€™ll go back to this soon - Self signed for now

FIXED - continuing past that and creating the nextcloud.conf stops apache from startingā€¦ This was resolved by cd /etc/apache2/sites-enabled then sudo rm nextcloud.conf - SOLVED - USER (ME) Errorā€¦

2 - Editing the Nextcloud.conf with the follwing breaks my nextcloud (Internal server error):

ā€˜memcache.localā€™ => ā€˜\OC\Memcache\Redisā€™, ā€˜memcache.lockingā€™ => ā€˜\OC\Memcache\Redisā€™, ā€˜filelocking.enabledā€™ => ā€˜trueā€™, ā€˜redisā€™ => array ( ā€˜hostā€™ => ā€˜/var/run/redis/redis.sockā€™, ā€˜portā€™ => 0, ā€˜timeoutā€™ => 0.0, ),

and Htacessā€¦ SOLVED - Wrong place breaks, correct place worksā€¦ Learningā€¦

4

https://www.c-rieger.de/
or

5

You need to put all of that in your config.php file, not the Apache conf file :slight_smile:

And when you do, pay special attention to formatting, making sure there are commas at the end of all but the last lines in the config file, etc

6

Thanks Jason! Iā€™ve got all that done now, It was indeed a missed comma

Nextcloud is up, Apps are enabled as per PoC requirements

Now, Itā€™s my Nemesis, which is NXDOMAIN error stopping me getting a SSL Certificateā€¦

I may well need to post on letsencrypt for that

7

The guide didnā€™t literally want you to put ā€œcloud.domain.comā€, but rather, a DNS A or CNAME record that youā€™ve created for a domain you control. Youā€™ll need to make sure youā€™ve got such a record that points to your serverā€™s IP.
Example: if you own the site ā€œthisplace.hereā€, then log in with your DNS provider/registrar and add an A record ā€œnextcloudā€ in that domain that points to your IP, then you would replace ā€œcloud.domain.comā€ from the guide with ā€œnextcloud.thisplace.hereā€.

8

Hi,

I redacted my domain with cloud.domain.com

I have confirmed i have an A record in DNS, this resolves on both the server, and client machines.

9

Ok, sorry for assumptions. This A record also needs to be resolved correctly by LetsEncrypt, so it could well just be a cache timing issue. With most DNS providers, trying again in an hour or so will let it take care of itself.

10

No probs - I did post that iā€™m a newbieā€¦

Iā€™ll speak to a few colleagues tomorrow - both my nexctloud domains i have created do not work. They have been created for well over a weekā€¦