Commit failed (details follow): Server sent access forbidden and 403 Access Denied on the repository in response to DELETE request - apache

Apology for my week knowledge in svn. I am managing the Apache subversion svn server which is deployed in azure Ubuntu 14.04 VM. And on client side using the Tortoise client 1.8.8. I am facing the issue while deleting any directory or file from the repository. I thought of it is a permission issue but user can able to create, edit the file and commit the same without any issue. But for deletion and then committing the same is giving the error. Please help me out. For your better view I have enclosed the screen capture of the Tortoise client error. Issue:
Error while performing action: Commit failed (details follow): Server sent unexpected return value (403 Access Denied) in response to DELETE request
I am getting this error every time I try to commit
Update happen no issues not able to delete and commit anything what wrong...
Things I have done:
- I have given full 777 permission to repos for authenticated users.
- Also have checked the password and auth file for users password and authentication, that is also correct.
- And the same is working at my home. So, Is there any network or firewall rules which is creating issue?
Waiting for the resolution.

Related

Strapi: can't save anything in admin

I installed Strapi, apparently successfully, but anything I try to save gives me an error
Failed to load resource: the server responded with a status of 403 (Forbidden)
I have it installed on a centos 7 server.
I was even able to create a few content-types, but when I try to make relational fields I get this error.
I thought it would be something related to roles and permissions plugin. Tried to change permissions, but same error. Tried updating my profile, also error.
Ok, I just figured it out.
Mod segurity was on. Had to turn it off.

SVN Repository - can checkout but commit gives a timeout

I have configured a svn server and I can the checkout with no issue. But when I try commit, it takes long time and gives a "connection time out" error in Tortoise svn client. Does anyone have an idea how to resolve or where to check. seems this is a permission issue and I believe the user that I used has required write permission to the server.
Error
seems this is a permission issue and I believe the user that I used
has required write permission to the server.
This is not a permission issue. You have to check firewalls and your server configuration.
Does anyone have an idea how to resolve or where to check.
No. This is just a timeout error. You should revise your server configuration and check firewalls. There is a chance that your firewall rejects certain HTTP requests.

Weblogic Bridge Message - Failure of server APACHE bridge:

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.

IntelliJ PAM Authentication Failure on CVS Update after updating password

When I'm forced to change my Windows AD account password IntelliJ is no longer able to perform any CVS action (e.g. update) on any checked out class files.
Right-click on class file->CVS->Update
Then the Messages console appears with "Error: Authentication failed. Response from server was: PAM authenticate error: Authentication failure"
I manage to workaround this by clearing the .cvspass file referenced under Settings->Version Control->CVS. It doesn't feel like a very elegant solution. I would have expected a prompt of some sort to re-enter my new password.
Is this the only way to getting cvs to work after updating the password?
I did find a compromise (somewhat). No need to delete the entire .cvspass file. I just open it and remove the line that has the repo that's giving me problems at the time.

How to save subversion password with bzr-svn

I am using bzr-svn to chekout svn repositories using bazaar. But bzr-svn asks for passwords everytime, I searched the web to find out about authentication.conf
I put the following section authentication.conf
[something]
scheme=svn+http #tried http only or svn only
host=uuuuuu.com
path=/svn/project #tried without stating path
user=wwwww
password='mmmmmm' #tried without quotes
In all cases either I was prompted for password, or got the following error
bzr: ERROR: Permission denied: ".": OPTIONS of 'http://xxxxxxxxx/': authorization failed: Could not authenticate to server: rejected Basic challenge (http://gamernetwork.unfuddle.com)
I put the same snippet in bazaar.conf and subversion.conf, but I got the same results/errors.
How can I use bzr-svn without typing my password each and every time?
I learned from #bzr IRC channel that bzr-svn can use cached authentication info of regular subversion client.
You just have to checkout the project once with svn, saving the user name and password. After that, bzr svn can use this password.