Omni Web Server Problems

[Andrew Stolarz]

Jeff,

Some notes I have on this topic when we set this up.

1. In your IIS site bindings for the https domains. Do you have "require
server name indication" enabled?

2. Are you using a 32 or 64 bit version of omnisapi.dll /web server ? you
need to make sure you have "enable 32-bit applications" set correctly for
the app pool.

3. Do you get a valid response from omnisapi.dll? ie. if you run
https://yourdomain.com/cgi-bin/omnisapi.dll, does it come back with "bad
request"? (cgi-bin is simply a virtual directory in IIS for the domain).

4. Are you setting $ctask.$issecure in your app?



Andrew




On Mon, May 16, 2022 at 12:53 AM jgibson interceptsolutions.com <
jgibson at interceptsolutions.com> wrote:

> I'm curious if anyone has ran into this.
>
> We have a new application we are running on our web server.  We had it on
> a test domain on our server.  It's running Windows Server 2019 with IIS.
> We are running Omnis Web Server 10.2.
>
> We set up the domain initially on our server without setting up an SSL.
> Got it all configured and it ran perfectly.
>
> However, we needed to move it to the proper domain on this server that had
> our SSL running on it.
>
> We reconfigured the new domain with all the proper settings within IIS to
> point to the appropriate DLL's.  Pooling information, etc.
>
> If we attempt to go to the old domain that is just set up locally on the
> server, it works just like it should.  Application opens with no problems
>
> However, when we attempt open the application within our new domain, when
> we attempt to open it, we get the following error in Edge, Firefox, or
> Chrome.
>
> "An Error has occurred when communicating with the server. Press OK to
> retry the request"  If found this error in the documentation.  It's the
> very first Comms Error.
>
> If I keep pressing ok, the message keeps appearing until we press cancel.
>
> We know it's making it to our login page, because when we press F12, we
> get all the perinate info coming from that page.
>
> We've tried restarting IIS.  We've tried restarting the entire server.  No
> matter what, we continue to get this error.
>
> Obviously both of these domains are pointing to the exact same
> application.  Is there a problem running more than one domain on a server
> pointing to the same application library?
>
> Any thoughts or suggestions on this would be greatly appreciated!
>
> Thanks!
>
> Jeff Gibson
> Nashville, TN
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>