I just installed e107 v2 to my web host. I made a single new post on the homepage, but the time shows up as 15 Dec 2012 : 17:00. I can't find any other settings for it in the admin panel, just the formatting itself. I also can't seem to find any other known issues about it with e107. I made sure the timezone is correct, but that won't account for the year difference. Any ideas how to correct this ? The installation is automated, it does not ask for any user input except for mysql database credentials.
change it here http://localhost/e107_admin/prefs.php#nav-core-prefs-date Change the localhost to your server address
Related
I am working with Keycloak, version 19.0.3.
I am using it in docker container, using image
quay.io/keycloak/keycloak:19.0
I am using postgresql database.
I am hosting it on azure.
I had a working setup with a few clients, scopes etc. Everything worked fine. Then I tried to set up email provider to be able to receive email confirmations. I successfully received test email and I clicked save. Then after a while my session refreshed and I no longer can log in to the administrator console. I get the following error log:
2022-11-14T09:46:17.033164754Z: [INFO] 2022-11-14 09:46:17,030 WARN [org.keycloak.events] (executor-thread-191) type=LOGIN_ERROR, realmId=[realm_id], clientId=security-admin-console, userId=null, ipAddress=[ipAddress], error=user_not_found, auth_method=openid-connect, auth_type=code, redirect_uri=[redirect_uri], code_id=[code_id], username=[username], authSessionParentId=[authSessionParentId], authSessionTabId=[authSessionTabId]
During startup the following message shows up:
Failed to add user '[admin_user]' to realm 'master': user with username exists
However this user is nowhere in the database.
The administrator log in credentials are set up using environmental variables and the whole setup is still in dev mode.
This is not the first time it happened. It happened once before however I did not connect it to the fact that setting up email account might have caused it. I thought it was because I accidentally upgraded keycloak to version 20, so I started from the beginning.
This time I set up email and came back after 20 minutes. My username and password are invalid. I have them saved in autocomplete, so its not because I wrote my credentials wrong. Nothing else changed.
I thought that maybe its because I have my realm set up to use email as username, so I tested with email address I just added, stil nothing.
I struggled with it for a long time. I am at my wits end. Any tips are welcome.
I have the same issue. Not sure whether it was caused by SMTP setup.
I have checked the databases from the back-up and the new one (after day of work that also included SMTP setup).
The admin user_entity in the database was updated to my email address somehow with keeping the user id. So with my email address and original admin password I am able to sign into the master console.
I hope it'll help.
PS. I recall now that during first 'Test connection' for SMTP execution Keycloak asked me to type an email address for testing (where the test email is going to be sent). Now I think it is at that moment the admin username was changed to my personal email.
I have a website on Heroku that uses JawsDB MySQL. The app is crashing with "ConnectionRefused." When I try to log into the database directly through MySQL Workbench, it returns "unable to connect to localhost," suggesting to ensure that MySQL is running on the amazonaws.com address, that port 3306 is open, and that the username has rights with the right password.
When I go to the JawsDB settings page, the Server Status indicates the "Status" is "BACKING-UP." It's been that way for hours.
Is this something that Heroku needs to fix? Amazon? How do I get it unstuck? I'd dump the whole thing and start a new database except I would need to get a backup of my data...which I can't get because I can't access the database.
HACKERS BEWARE
This issue could be related to recent Heroku security breach on April 7 - April 13, 2022 where many Heroku accounts and our applications were compromised! The following is statement from Salesforce (Heroku) Security Team (5/4/2022):
"... Our investigation also revealed that the same compromised token was leveraged to gain access to a database and exfiltrate the hashed and salted passwords for customers’ user accounts. For this reason, Salesforce is ensuring all Heroku user passwords are reset and potentially affected credentials are refreshed. We have rotated internal Heroku credentials and put additional detections in place. We are continuing to investigate the source of the token compromise."
I contacted Heroku who then contacted JawsDB. They did magic in the background to move my DB to an alternative location on Amazon, and it was fixed.
I have a strange error appearing whenever I try to access my Piwik analytics.
It has been working fine for months and I haven't upgraded anything. The only change was that my account was 'on hold' for a few weeks due a non-payment mix-up. During this time my whole domain was unavailable.
I am on a shared hosting account with JustHost. I have both Joomla 3.8 and Piwik installed there under the one domain, Joomla continues to work no problem.
When is visit MyDomain.com/analytics I see the following error message;
Wondering if anybody would know what this means, or why it's happening. Is there something I should ask my host if they have changed? Surely it would also effect my Joomla installation too though (which it isn't)?
I have tried their support forums however it very quiet over there. It has been suggested to look in the following file piwik/config/global.ini.php and check that the database driver is defined, which it is. My config file contains the following;
[database]
host =
username =
password =
dbname =
tables_prefix =
port = 3306
adapter = PDO\MYSQL
type = InnoDB
schema = Mysql
I have created a phpinfo() page located at MyDomain.com/analytics/phpinfo.php I can see all the information, if anybody needs me to clarify anything or settings.
Any help or suggestions appreciated.
There was no .htaccess file in my MyDomain.com/analytics directory. As soon as I added one it worked!
I run a series of DTS packages via SQL Server (2000) Agent every night. They have been running ok for years until I added a couple of transform data tasks that pick up info from another local SQL Server (2008).
The odd thing is that the tasks run ok for about a week and then fail with the error 'Login failed for user domain\$duplicate-1889'. I don't run these packages using this user account, in fact I don't think it's a real account. I have a Windows account called dbadmin which has been set up on both servers to have access. This dbadmin account is used to start up the SQL Server Agent service and run the scheduled jobs.
When the jobs fail, all have to do to get them to run again is to stop and restart SQL Server Agent. But after a week they fail again with the same issue. Also, it's not the same day of the week each time.
I checked the Windows event log and although I can see the error, I can't figure out its cause. Any help or pointers would be appreciated.
The domain\$duplicate-1889 name looks like machine account. Every machine joined to a domain has such an account in the domain that the machine uses to authenticate to the domain.
The passwords for those accounts are automatically handled and the password is periodically changed automatically. By default that interval is 30 days but if is changed to once a week in your environment maybe there's a problem when the computer's password has been updated?
It is possible to disable the automatic changing maybe that's worth trying to see if the problem dissapears.
I'm trying to connect to our SQL Server box from our web server. The only thing i've been able to find regarding the issue is to enable tcp/ip and mixed authentication.
TCP/IP is already enabled
Mixed authentication mode is selected
we already have 1 user successfully connecting to a different database so I know TCP/IP and mixed authentication are working.
Logging in as the problem user from sql manager works fine.
I get the same error creating an ODBC connection as well as a ColdFusion SQL Server data source.
According to the log files, which isn't logging all the attempts also indicates State 40, which is "Default database could not be accessed (SQL 2008)."
I've check and the default database is the one I want to open. The Schema is DBO.
Any help would be appreciated.
Make sure your user password not longer than 16 characters.
I apologize for not answering this sooner. To be honest I completely forgot about the question until I got a 'Notable Question' badge from it. Unfortunately, I'm afraid it won't help anyone as the problem was caused due to bad information from the network admins. They moved our SQL server to another box but did not shut down the old instance. Essentially, they gave me the old IP to connect to. Once I got the correct IP to the new box everything worked perfectly. The user I thought was connecting was an older account that was already established prior to the 'move' so the account existed on the old box.
If your box has multiple IP's on it, make sure the Cold Fusion server's IP address (that it's binded to) is allowed access to the SQL box. I've come across this problem in the past. I don't know if you're using a firewall or not to restrict access...but this was a problem I've encountered in the past.