@theopenem_admin
It seems like ProvisionAuth.cs In toec api validates the uri it also looks like it for intercom.
I'm pretty sure that why i'm not getting pushed remotely correctly, i asked the reverse proxy to change the uri for what the toec api is waiting for but the toec api is not accepting the change, like if it was not reading my new http header, i'm pretty sure those 2 controllers needs to have reverse proxy support added
Best posts made by daymickcorr
Latest posts made by daymickcorr
-
RE: WAN Remote Access Issue
-
RE: WAN Remote Access Issue
I've added a rule to rewrite the hostname in the reverse proxy i'm still getting the same issue
what certificate does the toec client need intermediate ?
-
RE: WAN Remote Access Issue
@theopenem_admin
It's strange it tells me back that the certificates are invalid and it is giving me again the authorization issue, i'm reinstalling the certificates on both app and com server -
RE: WAN Remote Access Issue
Ok the app server contains the remotely files and the folder does not sync with the com server
-
RE: WAN Remote Access Issue
@theopenem_admin
Remotely has had a strange issue the installation failed on the client
When I try to run the deployment command manually I get this application cannot be executed on your pc and the installer weighs 0 bytes.I'm going to check on the remotely side I saw that there was a cors setting, How would i redeploy the remotely ?
-
RE: WAN Remote Access Issue
@theopenem_admin
Ok I installed the bad intermediate certificate, sorry I'll update soon about remotely -
RE: WAN Remote Access Issue
@theopenem_admin yes I can upload the certs if you want
I have generated the certificates with the public name set for the com server I don't know if this changes something