Search the Community
Showing results for tags 'port 80'.
Found 2 results
Anthony Girdler posted a topic in Custom Web PublishingHi, My programmer and I are trying to set up communication between FileMaker 16 and a WordPress website(www.heightspethospital.com.au ) so our veterinary clients can do online booking and look up when their pets are due for vaccination and other treatments. My programmer has hit a problem. The code does not work on the WordPress Server (www.heightspethospital.com.au), though it works on his local machine. He gets the following error: “Communication Error: (7) Failed to connect to 184.108.40.206 port 8080: Connection timed out” Filemaker error codes suggest this is a memory issue, but my programmer is sure it's not related to memory. He has tried re-installing filemaker server multiple times with no effect. I think he said the default port is 80, but that cannot be used for an unknown reason and he has chosen to use port 8080. The filemaker database is stored on: PC Windows 10 home 64-bit Filemaker server 16 Processor: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz (12 CPUs), ~3.3GHz Memory: 16384MB RAM Wordpress 4.8.1 hosted by SiteGround. Any answers or leads greatly appreciated. Anthony. PS. I don't know anything about programming and computer jargon, so I apologise if I have some of these terms wrong.
Has anyone used the 'Import XML data over http' feature at all? It could be one of the most powerful tools in the product if only they had developed it properly and finished the job! Sorry I'm having a bit of a whinge here as I cannot quite believe that no facility has been created for allowing proxy details to be entered. This is one of those slightly hidden or 'less-known-about' features of Filemaker which could now prove to be one of the post powerful. As demand for web usage and interoperability increases etc. how can this feature be left not fully developed?! I'm staggered. The reason we want to use this - and I'm interested to know if anyone else has used it, is we develop shrink-wrapped 'application'- like databases that are locked down but upgradeable. This means that the database has to behave like a real compiled application. It will not be accessed by developers once installed on the customer's computer and has to stand on its own feet, as it were. Customers' data sets are imported and exported in their entirety. But we were looking for ways for the database, once out there on its own, to access critical data (usually some sort of 'meta' data) from our servers. This allows us centrally, to control some of the behaviours of the product in copies already out there. Now the import xml data over http is such a slick and easy way to allow a database to 'draw-in' data without having it fully 'connected' to another database. All you need is an 'http' URL. It's utterly brilliant… Except, of course, Filemaker have only done half a job. They've implemented this feature without any proxy control. That means that this feature will not work on any organisation networks where they don't allow unfiltered internet on port 80. If any proxies are involved and the router/firewalls are not set to accept requests on port 80 it's utterly useless. In actual fact, that means this feature is useless in 90% of educational establishments, most of Asia where proxies are normal even on home connections and certainly a majority of businesses where their IT departments are particularly security-minded. So… that's most of the world then. Filemaker, how and where are you intending this feature to be used, exactly? Sorry to sound so irritated but, really! I think what winds me up so much about this is just how good this would be if it were finished off! The fact that Filemaker Server can serve xml data as a specific service is an indicator of how seriously Filemaker has taken it at that end of the equation. So how on earth is it that this feature can ever be used?! Does anyone use it successfully? And if so how are you getting around the proxy/gateway issue? Many thanks for reading by rant! I'm just so disappointed. Will