Community
Showing results for 
Search instead for 
Do you mean 
Reply

http 403 error

Avid Listener
Posts: 49
Country: aus

http 403 error

hi

 

cannot connect to server from a cleint machine

 

10.01 web

 

port 80 forwarded to router

 

 

error: http 403 forbidden

 

how to resolve this

 

suggestions please

 

assign

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: http 403 error

Can you open ACT! Web on the server - http:\\127.0.0.1\apfw

 

Can you get to the web server default page from your system - http\\IPorDomain (no \apfw)

 

How about from another machine on the same LAN as the server - http:\\IP\apfw

 

This would show if it's ACT! or your router

New Member
Posts: 4
Country: Australia

Re: http 403 error

Having the same issue accessing Act! externally at http://150.101.154.234/apfw

 

It is one of our Agents and we only require access as our secretary cleans/dedupes/corrects entries in her spare time

 

They are adamant nothing is wrong on their end but that is not the case.

 

It was working one day then not the next. No server changes having been made...

New Member
Posts: 8
Country: United Kingdom

Re: http 403 error

Act Premium for Web v11.1

 

Regularly get missing images/buttons. Regularly get 403 errors.

 

Running on an WinPro machine with 5 external users.  Removed firewall & anti-virus still having problems. 

 

It all worked one day and then not the next.

 

A restart seems to give us a 6 hour break.

 

Any help please. 

New Member
Posts: 4
Country: Australia

Re: http 403 error

This was quite some time ago but my issue with HTTP 403 on external access was due to the ACT! site in IIS being tightened down to only allow internal IP's (on a domain). It was setup by a third party and only used internally for some time, before the issue became apparent.
New Member
Posts: 8
Country: United Kingdom

Re: http 403 error

We obviously had this error, which looks like it has been resolved. 

 

Our webserver (on which ACT PFW  v11 runs) uses our main broadband in the office. 

 

We use this broadband for internal machines (laptops etc) and for our phone system (VOIP).

 

Because we used this line for our phone system, we had it set up to maintain a minimum bandwidth for our phones - Quality of Service on our Router -.

 

It seems that the ACT server requires a minimum bandwidth otherwise it issues these 403 errors every now and again when the bandwidth dipped.

 

By implementing a dedicated broadband line for ACT, we have resolved these issues. 

 

I would love it if Sage could have a check that clients can use to see if there is a bandwidth issue.