rattfieldnz / bitcoin-faucet-rotator Goto Github PK

Hi!

I've tried deploying your project. Site seems to work fine, however the login page upon entering the admin details gives the following output;

Whoops, looks like something went wrong.

1/1
TokenMismatchException in VerifyCsrfToken.php line 68:
in VerifyCsrfToken.php line 68
at VerifyCsrfToken->handle(object(Request), object(Closure)) in VerifyCsrfToken.php line 18
at VerifyCsrfToken->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in ShareErrorsFromSession.php line 49
at ShareErrorsFromSession->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in StartSession.php line 64
at StartSession->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in AddQueuedCookiesToResponse.php line 37
at AddQueuedCookiesToResponse->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in EncryptCookies.php line 59
at EncryptCookies->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in Pipeline.php line 104
at Pipeline->then(object(Closure)) in Router.php line 655
at Router->runRouteWithinStack(object(Route), object(Request)) in Router.php line 629
at Router->dispatchToRoute(object(Request)) in Router.php line 607
at Router->dispatch(object(Request)) in Kernel.php line 268
at Kernel->Illuminate\Foundation\Http{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing{closure}(object(Request)) in CheckForMaintenanceMode.php line 46
at CheckForMaintenanceMode->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in Pipeline.php line 104
at Pipeline->then(object(Closure)) in Kernel.php line 150
at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 117
at Kernel->handle(object(Request)) in index.php line 52

I've tried googling and adding CSRF token code, however nothing seems to change the error. Do you have any idea what causes this?

$ composer self-update && composer install
You are already using composer version 1.4.1 (stable channel).
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating autoload files

php artisan clear-compiled
PHP Parse error: syntax error, unexpected '{', expecting identifier (T_STRING) in /home/USERNAME/SITENAME.DOMAIN/routes/web.php on line 4
Script php artisan clear-compiled handling the post-install-cmd event returned with error code 255

I received this error from a user in my email inbox:

Step 4: I receive some errors when I try to run db: seed (line 1151 from Curler.php in app/Helpers/WebsiteMeta).

From testing, I see this error results when a url (either a faucet or payment processor) cannot be reached or is experiencing other technical issues. This is to be expected when a URL returns an error code 404 or greater. Instead of the error output being displayed in the bash shell, I'll instead log it to a file in storage/logs. I will also need to have a better think about how to handle 3** redirects.

Storing and seeding URLs uses a third-party library called https://github.com/onassar/PHP-Curler, which is used to check URL's for statuses and retrieve content. This library appears to no longer be maintained, so I either:

• A: Find another library that is regularly updated and provides unit testing
• B: Find another library that is regularly updated, does not provide unit testing, develop unit testing for the library myself.
• C: Find a library that isn't regularly updated, provides unit testing, analyse code base and unit tests, update unit tests as appropriate
• D: Find a library that isn't regularly updated, provides no testing, analyse code base, add unit tests myself
• E: Create a whole library myself from scratch, and integrate proper unit testing

To save time, I am inclined to go with 'A' - although the developer in me suggests B, C, D, or E. In saying that, I am also inclined to go for option E - the back-end components of such a project makes this option seem really appealing. So the short term solution will be option A, but perhaps start another project on the side, a-la option E.

https://codecanyon.net/item/btc-faucet-rotator-earn-passive-cryptocurrency/20550719

SomeOne is selling this on codecanyon

you need to report him