I have used a Linux SVN server with the PxPlus interface for years.  Basically you setup the SVN server on the Linux box and establish/save a SSH connection using putty.

Once this is done you can use the url of svn+ssh://puttySaveName/..directory.. in TortoiseSVN to browse/access the repository providing access to your Linux SVN server from Windows workstations.

Most routers will provide a port forwarding option which will allow you to forward a request from the internet for a specific port to be forwarded to an specific workstation behind the router.

You indicated that the workstation running ezWeb is running on the internal IP 10.0.0.71 port 8080.  Given this set your internet router to forward incoming requests for port 8080 to that internal IP 10.0.0.71 port 8080.  You should then be able to access your application using http://72.50.4.97:8080/inomads

If desired you can use the router to change the port number.  For example if you want set port forwarding of port 80 to port 8080 thereby eliminating the need for the external URL to include a port number since HTTP by default implies port 80.

Now if your router is connected to the Internet and it IP address is dynamic (that is your provider can and does periodically change the IP address) you might want to consider using a dynamic DNS service so that rather than using the IP address people can use a name to access your application.  Personally I have used freedns.afraid.org for a few years and it has worked well.

Assuming this is all set correctly you should be able to access your application.  If you are having trouble its possible your workstation's firewall might be preventing external access.  Try disabling the workstation firewall temporarily and see if that solves the problem.  Many firewalls have settings that allow local access through the firewall but prevent external network access.  If disabling the firewall works then check your firewall to make sure it allows public incoming access to port 8080.

PxPlus only had JSON support as of version 11.  Version 9 is from 2010.

Just checked and it appears smtp.office365.com does claim to support standard SSL connections on port 465. Using this port should allow you to simply use a initial SSL/TLS connection avoiding the need to issue STARTTLS.

Why wouldn't you simply use the standard mail interfaces included with PxPlus.  Simply convert your existing home-grown interface to call the standard interface so your application code remains the same for the most part?

Phil

You can use the img tag in webster, however the image source will need to be directly accessible through the Internet.  This is likely something you won't want.  For example if the image had sensitive information such as a payroll stub or invoice with pricing you would not want to have the images directly accessible.

Using the [picture] shortcake allows you to display any image (or pdf) from any directory as long as the requesting browser is signed on to the system with appropriate security.  This is done by encrypting the full pathname of the file being requested within the src= used by the img tag generated by the [picture] shortcake.  This renders the value in the src= useless by anybody other than the desired end user whose encryption key is maintained by Webster.


Mike

Phil

Actually the picture short code is designed to make it easier and more secure to display images. 

Basically you can have the system show a picture from any location/directory as the system will generate code that encrypts the pathname forcing user security to be applied.  This means you don't have to place images (which could contain sensitive information) on a directory that can be directly accessed via URL.  The encrypted pathname is based on a key that is specific the user making the request therefore providing additional security.

Glad this helped your resolve your issue.

If you look at NGINX documentation it will describe the headers that may get added.  In particular the X-Real-ip header which is described at https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/

Is it possible you did not router STDIN and STDOUT to /dev/null for the SimpleCS server process?
Alternately are you runnin any other PxPlus processes on the server?

One thought -- you said you are using different versions of ProvideX (this should be PxPlus otherwise you need to contact Sage).  Given this please doublecheck that all versions are  the same -- either 64 bit or 32 bit. 

The display of installed ActiveX controls will vary between 32 and 64 bit installations as each will depend on the software installed and whether it was 32 or 64 bit.

You should install and use the WindX plugin to connect and not the installed PxPlus as that will cause double user counts.

Sigsign/Sigplus are from Topaz systems.  You may need to contact them as to why the difference.

According to https://topazsystems.com/software/sigsign.pdf sigsign uses sigplus.

If you want to drop files from Outlook attachments they first have to be dropped into physical files in a directory.

What I have done in the past is create temporary directories where I have the user drag whatever they want.  I display the temp directory using the windows File.Explorer Com object.  It will accept just anything and convert them to files.  Simply create a dummy directory then point the file.explorer Com object to it. 

Use the DROP FILE directive.

See External File Droping in https://manual.pvxplus.com/page/directives/drop_on.htm

Phil

I would suggest you try a different user -- either NETWORK SERVICE or a standard user on the system.

Regards
Mike King