I have a azure service running wordpress.
Someday, I updated a plugin (Yoast SEO) and stopped work. Azure's KUDU panel cannot shows files.
Look:
I can list using command ls-l, but KUDU panel no.
I tryied chmod, chown and nothing.
More special is when I changed directory to this folder and receveive response my session is expired. But it is not. I get use other feature with same session.
If I access using direct URL, I receive:
"You do not have permission to view this directory or page"
I have a Microsoft support but it not helps.
Anyone, please!
Microsoft support has concluded that there is a plugin that can be used in the Application Service called Composer that does not allow the word "vendor" and with this, the error.
We have disabled this extension and the site has returned to normal operation.
Hope it helps.
We have JIRA-Software 7 running on a custom docker machine with a Postgres DB and nginx as a reverse proxy (SSL). The custom domain is https://jira.url.de and is working so far. Installation has not been a problem.
But now i wanted to install a plugin and i get the following error:
An unexpected error has occurred. Please refer to the logs for more information.
First of all where can i find the logs?
Second - i found out that if i click on "Manage Add-on i will be directed to a 500 error on http://127.0.0.1:8080/plugins/servlet/upm
I read somewhere about configuring the server.xml file in order to correct the plugin url. But how can i edit this file? I can not find it inside the docker container.
UPDATE
if i try to update the Atlassian Universal Plugin Manager Plugin i get the following console Notice:
[blocked] The page at https://jira.url.de/plugins/servlet/upm was not allowed to display insecure content from http://127.0.0.1:8080/rest/plugins/self-update/1.0/.
If by clicking to Manage Add-ons you will go to loopback IP Address, most likely your Base URL is not configured properly. Thus, I would say ensure that your base URL configured properly.
Other than that, you need to ensure that you do have proxyName and proxyPort configured in server.xml file. I would say check this document for full details about Nginx configuration.
Lastly, installing plugin from UPM requires access to Marketplace. Thus, you need to ensure that your docker image is able to communicate with Atlassian Marketplace.
Hint:
Monitor atlassian-jira.log file which is in home directory of the jira. That way, you will get better information from the logs.
I'm trying to upload my symfony2 project on godaddy, on a sharing host.
I have several problems like a message : No input file specified when i login, register or other action.
Do you know something about this error message ?
I'm pretty sure that's related with the PHP version is running on godaddy server. But it should be related also with another tools they use for compilation process.
I had created a folder in my site, and uploaded drupal in it. But when I access it, the following error is coming
Internal Server Error
The server encountered an internal error or misconfiguration and was unable
to complete your request.
Please contact the server administrator, webmaster#xxxxxx.xx and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
There are literally thousands of things that can be wrong
Do you have access to the webserver logs? Check /log/apache/error.log for errors.
Have you already configured drupal correctly? Normally, when you surf to the drupal root directory, you get presented with an installer message.
Does your server support PHP?
I'd recommend any of the following:
Checking that you meet the Drupal requirements
Re-uploading the whole Drupal folder
Testing the Drupal folder (is this a custom installation, or just straight from the drupal website?) on local LAMPP webserver.
Assuming you're trying to run Drupal for the first time (ie run the installer), have you followed the pre-install setup?
Here's Drupal's "Quick install guide for beginners": http://drupal.org/documentation/install/beginners
Since you've already uploaded the code and you have your domain set up, you can probably skip down to the big labelled "Create the configuration file and grant permissions".
The first thing in this section is to create your settings.php file. Drupal won't work without this. You also need to set its file permissions to that Drupal's installer can update it.
My guess is that this is why you're getting the error. Follow the instructions on the page I linked you to above and you should be okay.
You'll also need to have a database ready for use by Drupal. The Drupal installer will populate the DB tables, but you need to at least have the empty DB ready for it to use.
Hope that helps.
I am trying to FTP to a new FTP site I setup with IIS 7.0 for the Windows Server Web (64-bit) edition. But I get the above error when I try to login to this site. But I can login to my other FTP sites.
Also, when I select this website from IIS Manager, the FTP section does not display in the middle section although it does display in Action panel. And I cannot successfully login to this FTP site either.
I have checked and I have Log on locally selected. I do not have allow only anonymous connections. I have Access this computer from the network selected.
I restarted my IIS and FTP services also.
The one different thing I noticed about this website in IIS different from the other site that has FTP working is that this one there are 3 virtual directories beneath the site. And that when I click on any one of these 3, then the FTP strip does appear in the center pane. Make sense?
How can I debug cause of this error? Any SW tools I can use?
Have you tried logging in from the FTP server? If you do this, and have "Show detailed messages from local requests" enabled under FTP Messages, then you'll get a clearer idea as to why the login if failing. In my case I got the following message (I am using IIS Manager Users, and Passthrough authentication)
530-User cannot log in.
Win32 error: Access is denied.
Error details: Filename: \\?\C:\Windows\system32\inetsrv\config\redirection.config
Error: Cannot read configuration file due to insufficient permissions
To solve this I gave the NETWORK SERVICES user read only access to the config directory specified in the error message. I'm not 100% sure this is the right thing to do, but it certainly fixed this issue for me.
in my situation, I was missing Role Service FTP extensibility, which is actually allows IIS Manager Auth.
This is pretty tricky, as you could allow IIS Manager auth, but still it would not work until you have not installed FTP Extensibility
In my case I forgot to enable the Basic authentication
There seem to be many different possible causes. In my case, I was unable to login with the plain "username" with the same error as mentioned.
It was solved when I logged in with ".\username" instead.
For some reason the FTP client was trying to login with a domain account, while I just wanted to login with a local computer account.
Hope this helps someone.
Try submitting your credentials in this format:
UserName: Domain|Username
Password: secretSquirrel
I had the same problem, I removed the FTP site and followed this:
http://www.iis.net/learn/publish/using-the-ftp-service/configure-ftp-with-iis-manager-authentication-in-iis-7
Prerequisites - I set the permissions on the folders using the 4 command samples but this did not alone fix the issue, so I cannot in good faith say this step is needed, but it is what I did and it now works.
CONFIGURE THE IIS MANAGEMENT SERVICE AND ADD AN IIS 7 MANAGER -
Just do step 4, removing the existing user first and then re-adding them.
Creating a New FTP Site and Configuring an IIS 7 Manager Account -
All the steps here
CONFIGURE THE FTP SITE TO USE IIS 7 MANAGER AUTHENTICATION
All 12 steps here, including the "administrator" setting in step 5.
Then it started working for me, I am guessing when I did this without a guide I skipped something simple.
In My case I have made that user a member of IIS_IUSERS.
Using IIS Users.
Do not isolate users -> User name directory was working fine. Users started in the right folder.
When I was switching to Isolate Users -> User name Directory I had the following error:
Response: 530 User cannot log in, home directory inaccessible.
Win32 error: The system cannot find the path specified.
For some reason, you need to add the LocalUser virtual directory that points to your root.
It has to be that exact name and it's case sensitive.
That worked for me.
Per this knowledgebase article, you would need the log on locally privilege enabled.
http://support.microsoft.com/kb/200475
I had the exact same error. In my case, I was using a local user defined on the server running FTP. The username was very short (3 characters). I could "run as" this user on the server, confirming that Windows was Ok with it, and allowed it to authenticate. But when testing FTP, it would return User cannot log in.
Solution? I renamed the user to be longer (4 characters). Of course, updated its name under Authorization as well. Then FTP worked. Hope it helps someone!
For me, I've configured the IIS as per usual procedure properly. The anonymous authentication was working but specific user are not.
because, the user accounts were created in IIS. Actually it was also supposed to be created Windows local accounts.
Then it worked.
Please Check the security of folder which is use that ftp .
see if the user or group you select for that ftp is associate with security of that folder .
In my case I had to remove domain from user.
So, your user should be like username, not like domain\username.
Hope it helps to somebody.
For some reason my user was "locked". So I could "unlock" it at local user manager (computer management). Now it works fine. I hope it helps.
I would recommend checking FTP logs first. The status code will give you more information about the issue. Here is the explanation of the status codes: The FTP status codes in IIS 7.0 and later versions
I had this issue because my IIS didn't support passive mode. After entering data in FTP Firewall Support module, the issue was solved.
More scenarios from this post 530 User cannot log in, home directory inaccessible
Authorization rules. Make sure to have an Authorization rule that allows the user or anonymous access. Check “IIS > FTP site > FTP Authorization Rules” page to allow or deny access for certain or all users.
NTFS permissions. The FTP users (local or domain users) should have permissions on the physical folder. Right click the folder and go to Properties. In the Security tab, make sure the user has required permissions. You can ignore Shared tab. It is not used for FTP access.
Locked account. If you local or domain account is locked or expired, you may end up seeing “User cannot log in” error. Check local user properties or Active Directory user settings to make sure the user account is active.
Other permission issues. The user account may not have “Log on locally” or “Allow only anonymous connections security” rights.
I spent long time looking for a solution, I've tried every shared answer on the internet and nothing could solve the issue. It is an issue I was ignoring for years and I never could fix.
Ok, I've Plesk installed and I'm not sure if it has some effect on IIS FTP to do the following behavior ...
Using Process Monitor tool, and making ftp login request and watching the tool and doing your investigation using this tool, you can get a hint about the REAL reason of the problem.
For me, I found out that IIS FTP was trying to access the ftp folder from a path DIFFERENT than the actual ftp path I've set, I do not know why, but maybe Plesk has some effect on this.
The actual ftp path is
C:\inetpub\vhosts\zidapp
The path that IIS FTP was trying to access DURING the login process is
C:\inetpub\vhosts\Servers\7\localuser\zid_app_ftp_user
I fixed the issue by creating a folder link from 'actual' folder path to the path IIS was trying to access - using the tool mklink tool
CMD command
mklink /d C:\inetpub\vhosts\Servers\7\localuser\zid_app_ftp_user "C:\inetpub\vhosts\zidapp"
I've fixed the issue that way, so wen FTP is trying to access the folder from the wrong path, it is now goes to the correct one.
Please note doing folder shortcut wont work for this, you need a link like linux, not a shortcut ...
I hope it will help you :)
You can check the reference account you are using to log in.
Mine happened to be locked out causing the 530 error.