I am using the docker image setup described here: https://www.azerothcore.org/acore-docker/
I was able to get the server up and running and work great for myself on my machine. I'm able to login and play. I set the client to look to localhost for it's target. Worked great.
I wanted my wife and daughter to be able to login as well. I successfully created their accounts, installed the clients, and they are able to login to my server (i.e. the password check is successful).
However, when the see the realm list, and make a selection, they are immediately redirected to the realm list select screen again.
I've found this topic (How to resolve sticking in "Realm Selection"?), which looks like it might help me resolve the issue, but I can't figure out how to open the mysql connection to the right database.
Can anyone help me work through this with a bit more details, please?
Thanks!
Okay, I know it may sound stupid but I really need your opinions or suggestions about something. A computer has an older WAMP version (5 1.7.0) installed in it (I'm not the one who installed it) and running on Windows XP. Whenever I go to its Phpmyadmin page, it automatically gives me access to anything what are in it. That's a security hole that must be solved. I want it to ask me or prompt a login page first. I still have no success from the following steps that I've tried:
I have set the username as root and the password as
samplepass from the Priveleges section in the Phpmyadmin page - Still no success!
I also modified the config.inc.php file. I put the said password in $cfg['Servers'][$i]['password'] and changed the "cookie" as "config" in $cfg['Servers'][$i]['auth_type'] - Still no success!
Already restarted the connection of all WAMP services after the changes made - Still no success!
I also cleared the histories, caches, cookies, etc. in the browsers just incase - Still no success!
One thing I've noticed is that the file has no $cfg['Servers'][$i]['AllowNoPassword'] nor $cfg['Servers'][$i]['AllowNoPasswordRoot'] in it. I tried including that into the file and providing it the value as "YES" but still, no login page is displaying.
I don't want to reinstall the WAMP or install new one. I'm afraid to destroy what was already there. So what do you think why the login page is still not displaying? Am I forgetting something or missed to do? (Sorry for sometimes I'm forgetful).
Alright, just after trying the things out again with still no success, I came up with this:
I changed back the value of $cfg['Servers'][$i]['auth_type'] from "config" to "cookie"
Then I added a random text value for $cfg['blowfish_secret']
After the (2) changes I made, I restarted the all the services again and poof! Login page is now displaying! But I'm still confused why my first tries didn't work. I'm not a know-it-all person about this particular area and sure there's more things to know about database thing. That's all.
I am not an IT person, using ubuntu 12.10.
I am trying to setup sahana software in openshift. I followed the guidelines from this page. It works fine until the point where I should use administrative interface. I tried every single possible password related to openshift, but none worked. It also only gave me four chances.
The guideline said, "Once your app is up you'll need administrative access to continue. For the admin app to work you need to put your password hash in parameters_8080.py in wsgi/web2py/."
I found the parameters_80.py but have no clear idea what to do with it. I tried to use htpasswd to create a new parameters_80.py but the admin interface still rejected me.
Can someone help me?
Thanks.
I think this thread seems to answer your question https://groups.google.com/forum/#!msg/web2py/DJvC9FMNohE/NykebQn5eUQJ
Some users trying to visit my website are getting a warning explaining "This is probably not the site you are looking for".
One of them sent me a screenshot (I'm sure we've all seen this screen before at some stage):
I'm using an SSL cert signed by StartSSL. It's signed for shareshaper.com and www.shareshaper.com.
You can see that the screenshot says that the user attempted to reach www.wamrc.com. I've never heard of that site before. For some reason though, when I visit www.wamrc.com I end up on my staging server.
I've tested my SSL setup with a number of online testing sites and they all report that everything is fine. I can't seem to replicate the issue myself.
What could be causing this error?
Some Other Thoughts
I have another StartSSL certificate I use on my staging server. This one is valid for staging.shareshaper.com and (I assume, can't quite remember) shareshaper.com.
One user who get the warning was using iPad Safari. Another OS X Chrome.
wamrc.com appears to belong to some dude called Oscar Arbelaez.
The issue was initially reported in this Reddit thread
For example it could be an incorrect DNS A-record for www.wamrc.com (pointing to your IP), or an incorrect cname for the same one, but all this is essentially included in the message in the screenshot.
Your server is misconfigured. Its reporting itself as www.wamrc.com.
You need to talk to your hosting provider.
I've been having this problem on one of my Joomla sites for a while....when trying to login at the backend, the page just refreshes to the login form again. The same thing happens for the login at the frontend.
After some searching, I came across this link but I've tried all the suggestions there and none work for me. Plus my database tables are all OK. On my local setup, the site works just fine...I just imported the database to the hosting server. Then used SSH to restore the zip file from my computer.
Any ideas?
This time, for me to fix the issue, I had to change a line in the config.php file.
I changed
var $session_handler = 'database';
to
var $session_handler = 'none';
I'm not sure if it makes a difference to this particular task, but I also have a non-standard
var $lifetime = '60';
Thank you very much. Had a tough time before I found this solution, thank you.
We are a small uk Web Design agency, Joomla is our CMS of choice.
I/We've had this problem a few times. Actually, yes this problem does occur most noticably during server migrations.
This time, for me to fix the issue, I had to change a line in the config.php file.
I changed
var $session_handler = 'database';
to
var $session_handler = 'none';
Im not sure if it makes a difference to this particular task, but I also have a non-standard
var $lifetime = '60';
I can remember that last time, I had to empty the session table also (probably jos_session for you , unless you have picked a different prefix)
And this is how Jim fixed it for me, hope it works for you.
I had a problem very similar to this a while back. PHP wasn't able to write to it's session directory (or it didn't exist), so it just kept dropping sessions on login.
You can find this directory in the PHP.ini file. I think it's called session.save_path On Ubuntu it was in /var/lib/php5.
I too, have had this issue in Joomla 2.5 when using SSL. The admin panel will be working fine, and suddenly I could not login.
Turning off SSL (which is not an acceptable fix) worked, but I tried adding
public $cookie_domain = 'yourDomainHere.com';
in configuration.php and it seems to be working correctly for now.
I found this:
session.cookie_secure must be set to 0
add this to you server php.ini
session.cookie_secure = 0
or local php.ini
restart apache
f you are on Joomla 1.7 or 3.4 then here's my research and solution:
The admin doesn't works when you accidently disables the plugins related to user authentication or login.
Joomla 1.7 and 3.4 doesn't have jos_users table, and instead it stores all plugins in jos_extensions table for 1.7 and init_extensions for 3.4
Solution except if you are using a different prefix for your tables
Go to jos_extensions or init_extensions table and look for plugins like plg_authentication_joomla, plg_authentication_ldap, plg_user_joomla, com_login and com_users.
Once you find them then make sure they are enabled in jos_extensions or init_extensions table.
Update the enabled column from '0' to '1' for all above columns (plugins) in jos_extensions table, and make sure you hit the 'Go' button to save the updates to database.
Voila, and you are now back to the login admin form.
The post was helpful to me since it gave me enough pointers to find the exact root cause. However the original solution of this post was for Joomla 1.5 and 1.7 but I had to dig in for Jooma 3.4 and managed to fix my problem.
Thanks everyone for sharing and good luck!