I am very new to Drupal. I have done the local setup and the front end is working fine. Now I need to login to the admin interface. Seems like there is a SAML configuration and when I try to access the /user/login page it is showing the following error :
The website encountered an unexpected error. Please try again later.
I can see there is one simplesaml folder in the codebase and I think this is handling the SAML login. Now in the local setup, I don't need to use SSO, but not sure how to disable this extension. I have checked in the core.extension.yml, but the fllowing extensions set to 0 there and hence I think this is not activated.
basic_auth: 0
externalauth: 0
simplesamlphp_auth: 0
Also in my local configuration settings.local.php, it is set as false:
$config['simplesamlphp_auth.settings']['activate'] = FALSE;
It will be very much helpful if somebody can guide me in the right direction. I have access to the database, but not sure where I need to make changes. This might be a simple thing, but I am blocked here.
The Error I am seeing the logs is like this :
Uncaught PHP Exception SimpleSAML\Error\Exception: "Could not find the metadata of an IdP with entity ID 'localhost:default:entityId'" at /vendor/simplesamlphp/simplesamlphp/modules/saml/lib/Auth/Source/SP.php line 317
You can login to Drupal using a console command.
Open a terminal, navigate to the project folder like
cd ~/project/my-project/web/
Then run
drush uli
the output will be a one time login link.
Related
i am currently getting information from my company's sharepoint page and display it on my asp.net project. I am using ClaimClientContext for authentication, and of course in my local host it is working fine.
However, when I publish the site and place it on my server the following error occurred: The requested site does not appear to have claims enabled or the Login Url has not been set.
The error is pointing to the Url which i have stated in my code:
Using ctx As ClientContext = ClaimClientContext.GetAuthenticatedContext("https://abc.sharepoint.com/team/Wiki/")
Any idea on how I can overcome this error? Do let me know if more information is needed, and i will gladly provide. Thank you.
Ok. After struggling with this for quite a bit now, I was able to resolve the issue. Its something to do with oAuth2 not supporting old protocols.
You can resolve with the below power shell commands
Connect-SPOService -Url https://<yourdomain>-admin.sharepoint.com -credential <adminIDwithElevatedPrivileges>
Set-SPOTenant -LegacyAuthProtocolsEnabled $True
You might have to wait for sometime after running this command.
Hope this helps!
I'm trying to add a custom domain to an existing project but keep getting the error that "this domain is already in use." I'm not using this domain anywhere else in any other project.
There is only 1 other forum post (http://grokbase.com/t/gg/firebase-talk/165r5n78nq/firebase-domain-is-already-in-use) about this error but following the step provided leads to zero results.
If you are getting that error it means that you're already using the domain in a project. You probably deleted the project but did not disconnect the domain before it was shut down. In this case, you can either wait for 10 days from when you deleted the project for it to be removed or,
you can restore the project by going to the Firebase IAM & Admin console click on projects pending shutdown.
Then proceed to disconnect the domain from the project like you normally would. Now you can use that domain again with no problem.
Go to https://console.firebase.google.com/iam-admin/iam/project and click on 'Projects Pending Deletion" click Restore. Then go to https://console.firebase.google.com/project/YOUR-PROJ-ID/hosting/main and delete the domain connection(s).
That should free the domain up for a new SSL cert.
if you are using appname.page.link make appname uniqe
Keeps showing:
Please configure app/js/config.js before running!
I updated my Firebase URL in config.js, enabled email/password and anonymous login in Forge.
Even changed text in the above error msg to:
"TEST Please configure app/js/config.js before running!"
, in app.js -- and my modified text doesn't show up even. Why? I restarted the web server between changes.
node scripts/web-server.js
Crazy, I can't figure this out.
I figured this out. I also had the ZIP archive in my Trash folder on Mac OS, somehow my console was in my Trash path, (no friggin idea how it got there, as I never cd'd to it), hence changes to my main folder weren't getting detected by the web server running on my Trash folder. Stupid user error -)
How can I check Drupal log files?
I'm using Ubuntu 10.10 + Apache2 + PHP 5.33 + MySQL and Drupal 7.
To view entries in Drupal's own internal log system (the watchdog database table), go to http://example.com/admin/reports/dblog. These can include Drupal-specific errors as well as general PHP or MySQL errors that have been thrown.
Use the watchdog() function to add an entry to this log from your own custom module.
When Drupal bootstraps it uses the PHP function set_error_handler() to set its own error handler for PHP errors. Therefore, whenever a PHP error occurs within Drupal it will be logged through the watchdog() call at admin/reports/dblog. If you look for PHP fatal errors, for example, in /var/log/apache/error.log and don't see them, this is why. Other errors, e.g. Apache errors, should still be logged in /var/log, or wherever you have it configured to log to.
If you love the command line, you can also do this using drush with the watchdog show command:
drush ws
More information about this command available here:
https://drushcommands.com/drush-7x/watchdog/watchdog-show/
Make sure drush is installed (you may also need to make sure the dblog module is enabled) and use:
drush watchdog-show --tail
Available in drush v8 and below.
This will give you a live look at the logs from your console.
We came across many situation where we need to check error and error logs to figure out issue we are facing we can check by possibly following method:
1.) On blank screen
Some time we got nothing but blank screen instead of our site or message written The website encountered an unexpected error. Please try again later , so we can Print Errors to the Screen
by adding
error_reporting(E_ALL);
ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);
in index.php at top.;
2.) We should enable optional core module for Database Logging at /admin/build/modules, and then we can check logs your_domain_name/admin/reports/dblog
3.) We can use drush command also to check logs
drush watchdog-show it will show recent ten message
or if we want to continue showing logs with more information we can user
drush watchdog-show --tail --full.
4.) Also we can enable core Syslog module this module logs events of operating system of any web server.
We can use drush command also to check logs
drush watchdog-show it will show recent 10 messages.
or if we want to continue showing logs with more information we can user
drush watchdog-show --tail --full.
MAMP/logs/php_error.log
Above all given option does not work go to the MAMP/logs/ check all type of log-like.
mysql_error.log
nginx_error.log
apache_error.log
For drupal 9, you can access to your logs with drush , here some commands:
watchdog:delete (wd-del, wd-delete, wd) Delete watchdog log records.
watchdog:list (wd-list) Interactively filter the watchdog message listing.
watchdog:show (wd-show, ws) Show watchdog messages.
watchdog:show-one (wd-one) Show one log record by ID.
watchdog:tail (wd-tail, wt) Tail watchdog messages.
One more thing if your are not fan with commands, please in the Administrative menu, go to Reports > Recent log messages. On this page is a list of recent log messages which you can filter by type and severity.
but if your are professional you can configure ELK that's will give you all
In Drupal, you can check the log files through the Drupal admin interface or by accessing the server files directly. Here are the steps for each method:
Through the Drupal admin interface:
Log in to your Drupal site as an administrator.
Go to Reports > Recent log messages.
This will show you a list of recent log entries, filtered by severity level and type.
By accessing server files:
Connect to your server via FTP or SFTP.
Locate your Drupal installation directory.
Look for the "logs" directory or server level /var/log.
Open the log files you want to view.
Note: The location of the log files may vary depending on your Drupal installation and server configuration. You may need to consult your hosting provider or server administrator for help finding the logs.
There are a couple of other questions on here regarding this but they are old and have not been answered satisfactorily IMHO.
I am getting this error - "Unknown record property / related component
"permissions" on "sfGuardUser", referer:" - in my error_log when I
attempt to login to my symfony 1.4 app after deployment. I do not get
it on my local machine.
When I submit the login form, Symfony throws a 500 error. If I refresh
the page, the login form is reposted and I am logged in.
Can anyone suggest what might be causing this?
The answer can be found here: http://oldforum.symfony-project.org/index.php/m/102097/
The solution is:
rm ./lib/model/doctrine/base/BaseSfGuard*
./symfony cc
from http://oldforum.symfony-project.org/index.php/m/102097/
It seems that at some point I had this relation defined in my own schema file and this had been cached somewhere. When I moved the code to a new server without the cache, Symfony generated classes in a location which overrode the plugin's versions.
When I submit the login form, Symfony
throws a 500 error. If I refresh the
page, the login form is reposted and I
am logged in.
What browser do you use? I have same problem,but only in Opera...
I don't like using build all commands. If an SQL statement fails, building all can delete data. Never user build all commands on a production environment for Symfony.