can't log in

Hi, Narcisz, & welcome to the WordPress support forum.

Firstly, thank you *so much* for providing a site url–you have no idea how helpful that is when trying to diagnose problems such as this.

You’ve got several things going on here, including:
1) SSL;
2) Quite a few plugins; &
3) A custom theme.

It does appear that you can log in by typing
http://www.arminarmvolunteers.org/wp-login.php
in case that’s any help.

I don’t see any evidence of any sort of login plugin being present, but having said that, I may not. You’ve got an awful lot of plugins going on, some of which appear to be duplicative in purpose, such as slider plugins. Please be advised that plugins can conflict with one another as well as slow down a site. You might wish to consider deactivating plugins you don’t need. If you’d like the wp-admin url to work, then my first suggestion is that you deactivate all plugins, revert to a default WordPress theme, and see if the wp-admin url allows you to log in. If it does, then your next step is to switch to your theme and see if you’re still able to log in using the /wp-admin url. If not, you know the theme is at fault. If so, then the problem is likely w/a plugin. Reactivate them 1 by 1, logging in each time. When the login breaks, you’ve found the culprit. During this process, don’t forget to clear your browser cache, else you might be seeing a cached version of your site & not be getting the real picture.

Please let us know if this helps (or not). Nice concept, btw!

Hi, Narcisz. Actually, I think that perhaps 1 of those out-of-date plugins had some out-of-date code that was causing a conflict, which in turn caused some site problems.

Let me ask you–do you have a wordpress.com key? You’ll need that in order to use both Akismet & Jetpack. If not, both plugins provide instructions on how to sign up for one.

Hello again, Narcisz. Could you please post your .htaccess file here? & please don’t hesitate to ask if you need help doing that. Thanks.

No problem, Narcisz. Sorry about the late reply–it was night time here & I went to bed.

When you go into your file manager, highlight .htaccess. You should have some options, 1 of which is ‘Edit’. Please click that. Your file should appear. At that point, please select all text (control a does it very quickly), & then copy it (again, control c does it fast). Then you can paste it into your next reply to this forum.

Please let me know if my instructions weren’t clear–haven’t had coffee yet, & whatever I say w/o that should be considered as highly suspect.

Just being truthful, Narcisz. Have had coffee. You can trust me implicitly now. Lolololol.

Unfortunately, that was a warning dialog, not the full file. Please dismiss the dialog by whatever means you can, & then copy the file. Things you might see in the file are:
#begin WordPress
#end WordPress
etc.

I’m so sorry–I realize this can be hard.

Hi, Narcisz. Ok–so this time we actually are going to edit the file. The part to change is:
#<Files xmlrpc.php>
#Order allow,deny
#Deny from all
#</Files>

Notice what I’m asking you to do is to put a # (shifted number row 3 on your keyboard) in front of those lines–or you can delete & copy-&-paste from here, but I advise the first way. Then please save the file & check to see if Jetpack is working.

You’ve also got an authentication portion in your .htaccess file that forces you to enter a username & password in addition to your WordPress login. That may also be interfering w/Jetpack. If So, I’ll show you how to comment out those lines as well, but let’s try this solution first, ok? Since I’m a certified, bona fide coward, I tend to be rather conservative in my suggested solutions.

Ok, please edit .htaccess so the lines look like:
#ErrorDocument 401 “Unauthorized Access”
#ErrorDocument 403 “Forbidden”

The other thing you may need to do is ask your host if they’re running Mod_security, & if any of those rules are firing to block Jetpack from connecting. They can tell you that by examining their server logs–I strongly suggest you demand they do so if this doesn’t help.

Lastly, may we please see the edited file once the changes have been made? Just–you know–to make sure I haven’t missed anything.

Narcisz, that looks excellent. Yes, I’d suggest emailing your host. Ask them to check their server logs for any mod_security rules firing on your site that might be preventing Jetpack from connecting, & to make any necessary changes. Tell them you’ve been in contact w/the volunteers at the WordPress support forum, & they don’t see anything in your .htaccess file that would be causing Jetpack not to connect. Do you perchance see any files called error.log or error_log when you look at the files in your file manager? If so, can you paste it here if it’s not too big, or, if it is, can you just include recent entries? Perhaps that can clue us in as to what the errors might be. You may wish to include at the beginning & end of the pasted error log file/entries, i.e.,

this is a line
this is another line
this is the last line

In the US keyboard, it’s located directly to the left of the 1 key on the number row. I can’t comment for any other keyboard layouts–apologies.