I was able for past projects to connect through filezilla. I followed each time this tutorial: https://blog.openshift.com/using-filezilla-and-sftp-on-windows-with-openshift/
Now, on my newly created application I cannot connect. I get these errors:
Error: Server sent disconnect message
Error: type 2 (protocol error):
Error: "Too many authentication failures for 56420afe7628e1bc3d0001b3"
Error: Could not connect to server
Thanks
EDIT: Its interesting because now I check some of my other websites wich were stored in filezilla site manager and 3 of the 8 have the same error. I have't modified anything to them. I tried with another FTP client (WINSCP) and all the sites work fine. I updated filezilla to the latest version and I still have errors. I can't explain myself why some sites work and some others simply doesn't work anymore without making any change...
Related
I am trying to create a federated authentication using the Keycloak and following the steps mentioned here: Setup User Federation with Keycloak
I have been using the port 10389 instead of 389 mentioned in the document. Everything seems to be working fine until the step where I am making the connection from Keycloak to LDAP.
When I provide the Connection URL as ldap://localhost:10389 and click on the Test Connection then I get the error:
Error! Error when trying to connect to LDAP. See server.log for details
I am not sure what's wrong because when I check in the Apache Directory Studio there everything seems to be working fine for me and I am able to get all the users list etc. I am not sure why I am unable to make the connection from Keycloak to LDAP.
I tried the following things but nothing worked for me:
ldap://localhost:10389
localhost:10389
ldap://127.0.0.1:10389
ldap://localhost:389
Stopped the docker in the dashboard and started again.
After trying a lot I found the solution. Posting the answer as it can be useful to someone else in the future.
I was using the localhost and 127.0.0.1 which was not working. Finally, I checked the IP Address of my system using the terminal (for mac ipconfig) and tried that and it worked:
ldap://192.168.1.12:10389
I have an Azure database setup of which I have included the below connection string as I believe it should be. Problem is when I try to run my client app in production, the server returns a 500 internal error. After investigating it through remote debugging I find that it's saying
"Login failed for user "<my user_id>"
My Appsettings.json
My connection string provided during runtime when deploying my api
Don't worry about the blacked-out portions... I've verified those to be the same in both.
Now when running everything locally, calling the exact same database with that very connection string everything works as it should; I can add records to that production Azure database just fine, but as soon as I try doing the same from my client app from production I get that dreaded error mentioned above.
Can anyone tell me what might be happening? I've been over and over this and it's driving me mad. I've even gone as far as changing the connection string to be Server=... I've made sure to append the # to the user_id. I believe I've tried just about everything I could find that wasn't 8 years old, including searching similar issues here... nothing seems to be quite like my issue exactly.
If you need more information let me know and I'll update my question.
Thanks!
EDIT: Adding this to show I've already added all of my output IPs from my api app service to my Sql server firewall. Can someone tell me if all my settings look good?
I've been unable to login to my site for weeks and weeks now. I've tried everything I can find on forums and still no joy (eg: viewtopic.php?t=719540).
A few weeks back my Joomla site backend became unavailable with the error message "Unable to connect to LDAP server".
I have not updated or changed the site in quite a while. It just started happening. So I've ruled out anything I have done.
I will say the exact steps I have taken:
In phpMyAdmin, accessed 'jos_extensions' and then 'plg_authentication_ldap'. Changed 'enable' from '1' to '0'.
Accessed 'jos_extensions' and 'plg_authentication_joomla' and ensured it was enabled. ie '1'.
Accessed 'jos_users' and found out I'd been hacked with many new users (with names like 'habxnkxl') had been added. All passwords were changed to things like 'jnsnbjhbx'. I removed all the unwanted users and changed all passwords for users.
Followed the steps in 'how to recover your password page' (http://docs.joomla.org/How_do_you_recover_or_reset_your_admin_password%3F) and created a new super user 'admin2'.
edit
Now, 'repaired' jos_extensions, jos_users and deleted plg_authentication_ldap.
I've consistently been re-checking the login throughout the process, on firefox and safari, and still get the same "Unable to connect to LDAP server" error message. Even when I have turned off 'plg_authentication_ldap".
Your help in this matter would be greatly appreciated.
Thanks,
Nicol
Joomla 2.5
Set :
Client id 1
Enabled 1
Access 1
This worked for me :)
Here in this case, when a client is trying to access a particular URI, they are able to get a SUCCESS response for GET, but for the POST message, they are recieving a 500 error. Which is nothing but INTERNAL SERVER ERROR.
please look at the ERROR below:
Weblogic Bridge Message
Failure of server APACHE bridge:
Cannot open TEMP post file '/tmp/_wl_proxy/_post_1818_8' for POST of 3978 bytes
Weblogic Bridge Message
Failure of server APACHE bridge:
Internal Server failure, APACHE plugin. Cannot continue.
Eventually this was resolved after giving a 777 permission to /tmp/_wl_proxy and the client was able to access the page SUCCESSFULLY.
If this is a permission issue, then apache should throw 403 error, but i dont know why it was throwing 500 error.
if there is a internal server error, then both GET and POST response should be 500, So if anyone can answer this , it would be a great learning experience. Thanks..!!
You many not want to give Write to all (777) permission to /tmp/_wl_proxy directory. Check which userID apache is running under and only give writer permission to that userID.
This could be also with tmp directory full.
Here is what I did to solve this problem:
Go to weblogic management console (http://:7001/console)
Go to the server section, you will probably find one of your servers' status not running. This is what I found in my case;
Some features couldn't be run unless you have administrative privilege, I advice you stop all servers and re-run them as an administrator as you follow your servers status in the administrative console.
If the above doesn't work, something has to do with your either report or form server configuration is hindering the servers from starting up. In all cases you need to monitor the administration console.
We run jenkins on a mac mini server and need to have it use OpenDirectory. (I took this up again after getting Nexus to work with OD.)
I went into the Manage Jenkins tab, opened up the LDAP config panel and it attempts to connect, but I am getting an error that it can't connect. I am trying to just supply a username and password.
So the reason I couldn't connect was the Manager DN has to be the complete FQ name, e.g. uid=root,cn=users,dc=ontometrics,dc=com.
Once I got that working, I was getting LDAP Error 49: bad credentials. To solve this, I found a great LDAP browser that installed in a few minutes on the mini server: LDAP Manager. That helped me see the FQN for the root account.
One last thing: once I had the right account, it auth'ed, but then on saving the settings, I got an ERROR 500. Turned out, that was because I had a few spaces in the FQN, so do not do dc=ontometrics, dc=com. Then it worked and I logged in!
BTW, the mini server with 8 GBs of RAM runs Jenkins beautifully.