Jian, The plugin works now, but only when accessing the RedDot web interface while on the CMS server. Outside the CMS box, it still fails. So it seems clear the firewall settings are too rigorous for it to work outside that CMS server environment. So I would say you resolved the HTTPS aceess issue. Thanks! The CMS server is hosted offsite from the client. The client was getting a lot of attacks on the server so they set the firewall to accept connections from only a list of IP addresses, a range that they use for their workstations. If you have an idea on something to change on your side to make this work, that would be great. Or if you happen to have an idea on the firewall settings, even better. Seperate issue, at least now, do you find it rare from your experience that a client requires their CMS server to use SSL for the whole session with RedDot when it is hosted offsite? Rob
-- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out.
