Tag Info

New answers tagged

0

Turns out there were a couple of server configuration issues that we had to iron out. The server's DNS wasn't setup correctly. This just prevented us from accessing the internet and probably had no bearing on the slow authentication. The hardware firewall wasn't properly setup either and as a result of that, the server was being bombarded by failed ...


1

This is happening because that domain doesn't exist on DNS Servers. There can be two ways to access your website: Register the domain with a DNS Provider and map that DNS with the IP of remote server. Map the stated domain to the IP of Remote Server in your host file. I'll recommend you need more about Domains and DNS. A good start can be: ...


2

You're confusing "distributed mode" (having the web server and CF server on separate boxes) as being mutually exclusive with using a reverse proxy. In reality, they are two separate concerns. A reverse proxy is simply an alternative to using the standard web connector. It simply causes your web server (IIS, Apache, Nginx) to redirect requests for CFML ...


1

DISTRIBUTED mode or REVERSE PROXY setup would be providing mostly similar level of security but DISTRIBUTED mode would have additional HIGH AVAILABILITY & RELIABILITY server scenarios.



Top 50 recent answers are included