Oh I see, I thought just Enable/Disable with one click like other add-ons, so this isn't a bug? So should you write a simple note in Overview add-on's page for everyone knows how to Enable/Disable properly ?You should remove or comment out the code you added to the config file to ensure it is properly disabled.
You can comment it out by adding two forward slashes//
at the start of each line of code you do not want to run.
Host (Lets encrypt) <--> Cloudflare (Cloudflare wildcard certificate) <--> DigitalOcean
, DNS is handled via Cloudflare. DigitalOcean of course is refusing the connection to cloudflare, since I can´t add the cloudflare certificate to Digitaloceans settings and so it´s complaining about an invalid certificate.I'm using subdomain through DigitalOceanChris, thanks for this piece of awesomness.
Has anyone an ideo, how to use DigitalOcean with a subdomain , while using cloudflare and Lets encrypt ? My setting isHost (Lets encrypt) <--> Cloudflare (Cloudflare wildcard certificate) <--> DigitalOcean
, DNS is handled via Cloudflare. DigitalOcean of course is refusing the connection to cloudflare, since I can´t add the cloudflare certificate to Digitaloceans settings and so it´s complaining about an invalid certificate.
Thanks for your reply. Are you proxying your subdomain through cloudflare with a cloudflare wildcard cert or are you only pointing the subdomain in the cloudflare CNAME entry to DO, without proxying?I'm using subdomain through DigitalOcean
You need to run CLI command to create SSL wildcard for domain, and you need to verify TXT record while doing that, after that you'll get a fullchain.pem and prikey.pem, open that 2 files and and copy it, go into DO space and go to CDN setting, edit it and add new subdomain certificate, paste 2 files you were copied, and then you're done
Don't forget to create CNAME Record in your cloudflare to point it to DO space (Example: abc.ams3cdn.digitaloceanspaces.com)
I'm using with proxying through cloudflareThanks for your reply. Are you proxying your subdomain through cloudflare with a cloudflare wildcard cert or are you only pointing the subdomain in the cloudflare CNAME entry to DO, without proxying?
config.php
, and then went to install/index.php?upgrade/
, but get a fatal error:Error: Class 'League\Flysystem\AwsS3v3\AwsS3Adapter' not found in src/config.php at line 27
Yay for attachment support!I believe it may be the X-Accel-Redirect support (as it needs nginx todo a redirect to a URL), I'll run through the tutorial and see if I can figure out why it is breaking.
Please help !!!
I have a few forums that I'm setting up to 'host' videos.
I have setup 3 amazon AWS S3 hosting spaces, configured those, and with a test file, those are live and online.
I've uploaded the Add-on (For 2.1) and have setup the config file, and I just keep getting error 500 (site-wide) when I add the main 4 lines of code.
It's as if the add-on hasn't worked. It can't find the files or something. I have my server guy giving me a hand now. So hoping there's something we can do to test?
The main error we seem to get is
'XFAws\\Composor' not found in..../var/www etc etc
Proxy FCGI error it seems to be, PID 6941 (if that helps anything at all)
Any help?
should we download AWS SDK and place somewhere because simply adding these lines
gives errorsCode:\XFAws\Composer::autoloadNamespaces(\XF::app()); \XFAws\Composer::autoloadPsr4(\XF::app()); \XFAws\Composer::autoloadClassmap(\XF::app()); \XFAws\Composer::autoloadFiles(\XF::app());
The 2.1 version doesn't need those files as it uses the core composer support. The 2.1 version doesn't even come with a listener to reference those files.
Are you upgrading to the 2.1 version or is this a fresh install?
Actually, just coming back to this point, emphasis added.
If you say they're exactly the same, does that mean you still have the lines like\XFAws\Composer::autoloadNamespaces(\XF::app());
in your config.php? If so, note that those are in the 2.0.x only section of the description -- you don't do that for 2.1. You really just need thefsAdapters
override (after the add-on is installed).
Ah, just seen that in the Update section for the addon
View attachment 193296
Could maybe make it a little clearer on the initial install instructions page for XF2.1, unless I missed something else on the front page
$s3 = function()
{
return new \Aws\S3\S3Client([
'credentials' => [
'key' => '1234567890',
'secret' => 'ABCDEF'
],
'region' => '',
'version' => 'latest',
'endpoint' => 'https://s3.cloud.cmctelecom.vn'
]);
};
$config['fsAdapters']['data'] = function() use($s3)
{
return new \League\Flysystem\AwsS3v3\AwsS3Adapter($s3(), 'BUCKET_NAME', 'data');
};
$config['externalDataUrl'] = function($externalPath, $canonical)
{
return 'https://BUCKET_NAME.s3.cloud.cmctelecom.vn/data/' . $externalPath;
};
We use essential cookies to make this site work, and optional cookies to enhance your experience.