The url was the same as the server (physics.ahsd.org). I did check site.conf. I originally had localhost for $server_root_url. I changed that to physics.ahsd.org. No change still getting 403 error.
Re: Forbidden You don't have permission to access this resource.
by Eric Stroyan - Number of replies: 5
In reply to Eric Stroyan
Re: Forbidden You don't have permission to access this resource.
by Michael Gage -Having it as localhost was probably causing troubles. Did you restart the server? That value $server_root_urlgets passed onto the apache server app only when it starts up.
In reply to Michael Gage
Re: Forbidden You don't have permission to access this resource.
by Eric Stroyan -I just stopped and restarted apache2. I'll restart the server.
In reply to Eric Stroyan
Re: Forbidden You don't have permission to access this resource.
by Michael Gage -shutting down and restarting apache should be enough. I've never had to restart the computer. Look closely at the error messages in the browser's development tools console tab and try to determine which url the browser is trying to reach when things fail.
In reply to Michael Gage
Re: Forbidden You don't have permission to access this resource.
by Eric Stroyan -
In reply to Eric Stroyan
Re: Forbidden You don't have permission to access this resource.
by Michael Gage -I’m not sure exactly where the problem is, but I think one of the errors at least arises because you are using http:// instead of https:// for the website.
The other possibility is that there is a permissions problem somewhere the files/directories instructor, pgProblemEditor2 AP_Physics/Tutorial/2/ chain.
When I try to put that address into the browser I get to the login page and I’m blocked, but you should be able to put in a username and password
and get to that problem and edit it. See what happens.
The url $server_root_url in site.conf is probably correct in using http: (and that seems to be what your site in general is using) but something
is asking for a secure connection back to the server (i.e. https) and doesn’t handle gracefully the fact that your site uses http. Almost all
sites now use https for the added security. The simplest fix would be to add an https (port 443) input to your site. It’s even possible to
configure it so that requests addressed to http:… are automatically redirected to https:. That might fix it and in any case it’s a good thing to catch
up with current practice and use https.