> a possible explanation why the app is accessible in v13 > is that your v13 server is already registered as an authorised app in > firewall settings. > > apps are registered by their absolute path, > so a v13 profile would not automatically transfer to v15, > because their paths are different.
See also: Tech Tip: Application-specific firewall rules versus Port-specific firewall rules http://kb.4d.com/assetid=77533 -------- When adding a firewall rule to the builtin windows firewall, the rule can be tied to either an Application or Port(s). * Application rules are tied to a specific location on the disk, and do not apply to applications that are installed or running from other locations on disk. When installing a new application (or update) to a different location it does not change these firewall rules to use the new location. * Port rules are tied to specific ports and will allow any application running on the machine to utilize the ports specified. This has the benefit of being able to change the software without needing to update the rules (provided that the same ports are used). Each of the two options has their own advantages. For example, Application rules have the added security that only the specified application can utilize the ports. While Port rules have the added flexibility that allows you to switch the software around without needing to add or modify the rules. If you are using Application rules be sure to update the rule when changing the version of 4D. If you are using Port rules be sure that all of the ports required by your application have been properly added to the rule. The default ports you will probably need are: * 19812 (SQL; used for 4D Client connections and external SQL; must be opened for 4D Client) * 19813 (App; used for 4D Client connections; must be opened for 4D Client) * 19814 (DB4D; used for 4D Client connectionl must be opened for 4D Client) * 80 (HTTP; used for non-secure web/soap; must be opened if using web or soap on default ports) * 443 (HTTPS; used for secure web/soap; must be opened is using secure web or soap on default ports). ----- Hope that helps, -Tim ________________________________ From: 4D_Tech <[email protected]> on behalf of Keisuke Miyako via 4D_Tech <[email protected]> Sent: Tuesday, April 3, 2018 10:39:33 AM To: 4D iNug Technical Cc: Keisuke Miyako Subject: Re: 4D Server v15 not displaying my database like others have already suggested, you might want to check the firewall settings. a possible explanation why the app is accessible in v13 is that your v13 server is already registered as an authorised app in firewall settings. apps are registered by their absolute path, so a v13 profile would not automatically transfer to v15, because their paths are different. > 2018/04/03 10:42、Andrew Hobson via 4D_Tech <[email protected]> のメール： > I'm lost here. What are the things I must check for ??? ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
