You don't have permission to access /scp/tickets.php on this server.

webed

HelloI keep getting the following error everytime i try to reply to a new ticket.ForbiddenYou don't have permission to access /scp/tickets.php on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

It's a new installation, nothing custom simply folowed the installer and i created a ticket from the frontend.

Is there anything i need to add/change in order for osticket to work? I folowed the specifications and my webserver is compliant.

Thank you

Energy

Im guessing you dont have chmod your webserver correctly? Are you running it on a linux server or?

webed

:)) that was the first thing i checked, 755 all folders 644 all files.

victor_r

groupfilesmust be on apache(depending of linux distribution), the files must be on root user.try with ls -alF on scp directory

webed

The problem is that this is happening only on some tickets. it doesn't happen on all tickets.I guess this is something made to happen, it's made like that to make you buy the hosted version.Thank you for your helpI will try another ticketing system.

ntozier

"I guess this is something made to happen, it's made like that to make you buy the hosted version."This is categorically untrue. The hosted version is running core."I will try another ticketing system."Good luck, and we hope that you find one that suits your needs.

webed

Thank you for your message but belive me, when basic features of a newly installed app behaves like that from the start it does not worth testing.Sorry for being "rude" but if you want to help the community release stable, well tested versions or offer proper support.Don't release semi functional apps and leave the community to fix it.

JRogers

@[deleted],No need for the lecture, this is not even an osTicket issue. You have a server permissions issue, plain and simple. If you want help with it, we might be able to help. You said "755 all folders 644 all files." That's completely irrelevant if we don't know who owns the files, and what account owns the httpd process (which by the way, you have not even told us). We don't even know for certain what OS your system is on, so you might start by providing the standard info when you ask for help. (rolling eyes).Given that your 403 error page doesn't even work (it generates a 404 error), I'm guessing you're shooting in the dark. We've all been there, but we don't need the lecture.And if you're really determined to use a different solution, try Request Tracker, by Best Practical. It's tried and tested, widely adopted, has a much larger feature set, and virtually guaranteed to send you running back here. ;)Jack

webed

Hello Jack,i didn't think it worth mentioning more details when this happens only on 2/10 tickets.Nothing special, just normal test tickets made from the frontend interface. If this was the case for all my tickets i would start diging and check permisions, owners and stuff but in the moment i saw it worked on another tickets that was confusing. I made 5 tickets with the same details as the first one, all worked that first one didn't. I made another ones and bam another random one not working.Really apreciate your help.

JRogers

Ok, I've had my share of rants, too. I agree osTicket's not perfect, and in some ways it's rough around the edges, but it works well for its intended audience.It helps to start here:Please read before requesting assistanceBased on the conversation above, it really looks like you're on Apache, probably on Linux. I agree that it's odd that this happens on random tickets. But to rule out the possibility that it's a filesystem permissions issue, please tell us:The username that owns the httpd process (apache?)The username AND group that owns the osTicket root directory (and any subdirectories that are different)Thanks.Jack

McGuyver

I have this problem too... Some times when I use some word with linux commands like: 'ping' , 'traceroute' , and others... It's really annoying! :-/