I have a site built with Laravel 5.2, and everything is running smoothly, but I keep seeing this in my logs:
'ErrorException' with message 'Route [baldeaglecontracting.home] not
defined
The way I have my routes configure, this means someone is trying to hit a baldeaglecontracting subdomain on my site like baldeaglecontracting.mydomain.com
What I can't figure out is, why would someone be trying to hit this same subdomian on my site over and over again?
Related
I am using the Strapi v3.0.0-beta.18.7 when I am trying to open the routes pages with the json, I see 404 error.
I had this error previously.
I solved it just started the new empty project and copied the /config, /api, /components directories in the
new project. But after some time it starts to show 404 again.
Starting a new project each time when Strapi through 404 error doesn't sound like a good solution.
Does anyone have an idea why does this error occur and how to fix or prevent it?
I have developed a Website on a dev environment, using Laravel and Socialite.
Months ago, I set up a project on Facebook Login in order to use it on my website. Login works fine on this environment, no errors.
Now I deployed it to a production environment, and set up a new FB Login for it. But now I got a generic error in the first login attempt.Image below.
Messages are in portuguese. In english: "An error occurred. Close and open your browser again".
If I try again, I get no errors, and Login works.
I have tried with 3-4 test users provided by Facebook, and with all of them the same occur: that error on first attempt, but works fine on a second attempt.
Use the same process on dev (create test user, try to login) and everything works fine. Login with no errors on first attempt.
The first project, for dev, was using API version 2.1. Update to 3.3 and everything continued to works fine.
The second project, for production, already started with API 3.3, and got all the errors described above.
As I copied all files dev->prod, every version (Laravel, Socialite... ) are the same on both environment. Just update hosts, users , database name (...)
Have now idea how to troubleshoot it.
Any help will be appreciate.
Strange problem: Have installed Laravels 'Valet' to serve sites from .dev locally. When I am in my 'code' directory where I parked valet and create say laravel new blog installed perfectly and spins up on blog.dev. However say I create laravel new test and visit test.dev I get 404 - nothing found ...? I removed everything and tried again but the same thing happens. Has anyone else had the same problem?
UPDATE
Interestingly, from that same directory 'code' If i run a ping on blog.dev I get returned packets and pings. However I do the same on test, I get bunch of help commands?
FURTHER UPDATE
So inside the project 'test' if I run php artisan serve I get a response of Laravel development server started: <http://127.0.0.1:8000> and If I visit the path bingo it works. But that confuses the issue even further for me...?
EVEN FUTHER UPDATES
So, I wish to add this iMac was a previous developers so the home folder is called Adam, I am a seperate user but also an Admin with my own folder sat next to it called 'Dan'but not a 'home' directory as such it is just in the sames 'Users' directory whenever I try to do anything I get errors like: ERROR: Notice: Undefined index: domain in /Users/Adam/.composer/vendor/laravel/valet/cli/valet.php on line 55 That was when trying to spin up laravel share
I have my laravel project and copied to another folder. I have changed the name of the app and my AJAX requests stopped working. GET works fine but POST,PUT methods either return '405 Method not allowed' or '500 Internal error'.
I am not acquainted with Laravel so could you please tell me what I possibly didn't do? Is there some REST config file where I configure routes?
I followed the setup to deploy laravel app on fortrabbit but now I am stuck with this error:
Error 403
Internal server error
Overload: More requests than the App can handle.
A script stops with an error. Are your config files up to date? Maybe turn on debugging to trace the error.
There is an error in the .htaccess file.
Something else. Please check the fortrabbit status.
I have checked the configurations but I keep find a cause for that or even a solution for this issue.
That's not really a good question to post her on StackOverflow. It's too specific - probably App- or even service-related. For such cases: please try customer support.