If you have just updated Plesk and server to latest packages, you might find yourself having issues with Let’s Encrypt. If you get following error while installing certificate from Plesk

Could not obtain directory: cURL error 6: Could not resolve host: acme-v01.api.letsencrypt.org 2; Name or service not known (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

Your openssl has probably been updated as well.

Simply restart of sw-engine and sw-cp-server should do the trick.

systemctl restart sw-engine
systemctl restart sw-cp-server

It’s best to restart php-fpm and nginx as well at this point. But might not be needed.

If you are developing new site, you have probably locked it through htpasswd. When you are done with og meta data, you might want to check it with https://developers.facebook.com/tools/debug/sharing/ – but facebook won’t be able to access your content, because you can’t give it your password.

You need to update your htaccess, from

AuthUserFile /.htpasswd
AuthName Disbait
AuthType Basic
Require valid-user
satisfy any
deny from all
allow from 127.0.0.1

to

SetEnvIfNoCase User-Agent "^facebookexternalhit" facebook
SetEnvIfNoCase User-Agent "Facebot" facebook
SetEnvIfNoCase User-Agent "Twitterbot" twitter

AuthUserFile /.htpasswd
AuthName "Restricted Access"
AuthType Basic
Require valid-user
satisfy any
deny from all
allow from 127.0.0.1
allow from env=facebook
allow from env=twitter

Credit coderwall.com/p/8y7t1q/whitelist-facebook-twitter-to-test-your-open-graph-and-twitter-card-implementations

Usually when you slide down your app screen, you will see gray, or white color background underneath your application.
You can change it by editing /platforms/ios/CoinWorth/Classes/MainViewController.m file.
Look for – (void)viewDidLoad and edit it like this:

- (void)viewDidLoad
{
    [super viewDidLoad];
    self.webView.backgroundColor = [UIColor colorWithRed:34/255.0 green:37/255.0 blue:43/255.0 alpha:1];
}

This will make the background dark-ish. 34, 37, 43 are rgb values, you need to divide them by 255.0 for UIColor.

To use black color( or any of the basic colors – just google UIColor ), simply do

- (void)viewDidLoad
{
    [super viewDidLoad];
    self.webView.backgroundColor = [UIColor blackColor];
}

Hi,

If you are doing a small API library in Laravel you may find the output json a little bit – especially with a small response this is caused due to cookies and headers sent together with the response.
For a small 400B response JSON laravel adds additional 500B ( more than 100% ) of cookie information.

To strip all this from response headers, you need to go to /app/Http/Kernel.php and update $middlewareGroups section
1/ add \App\Http\Middleware\ApiSession::class,
2/ comment out \App\Http\Middleware\VerifyCsrfToken::class,

Final section may look like this

protected $middlewareGroups = [
    'web' => [
        \App\Http\Middleware\EncryptCookies::class,
        \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
        \App\Http\Middleware\ApiSession::class,
        \Illuminate\Session\Middleware\StartSession::class,
        // \Illuminate\Session\Middleware\AuthenticateSession::class,
        \Illuminate\View\Middleware\ShareErrorsFromSession::class,
//            \App\Http\Middleware\VerifyCsrfToken::class,
        \Illuminate\Routing\Middleware\SubstituteBindings::class,
    ],

    'api' => [
        'throttle:60,1',
        'bindings',
    ],
];

Now create a file called ApiSession at /app/Http/Middleware/ApiSession.php with following content

<?php
namespace App\Http\Middleware;
use Closure;

class ApiSession {
    public function handle($request, Closure $next){
        \Config::set('session.driver', 'array');
        \Config::set('cookie.driver', 'array');
        return $next($request);
    }
}

That’s it!
In ApiSession.php you can check current api and only disable cookie for specific folder or url. You may do the same in VerifyCsrfToken class.

But if you project is strictly for API, this is the changes you have to make.