Thank you for your post.
Has anything changed with your database file? If the Container fields have been changed to external storage, be sure to open/include port 443.
If the issue still occurs, temporarily turn on all ports to make sure it works. Then, start eliminating most of the ports.
Nothing has changed. all storage is internal. I can access the files through a LAN connection but not throughout my static IP. Everything else in the DB is accessible accept container contents.
When I try to access them from the cell network, i get a different error that says "error 502, bad gateway - a bad response received from another proxy server or the destination origin server."
Thank you for the additional information.
Is the file being hosted with FileMaker Pro or FileMaker Server? What version?
Try creating a new layout and place only the Container field on the layout. Does this work?
Do you get the error for all entries in the Container field or just PDF file(s)?
Any other information you can provide may be helpful.
filemaker server V 126.96.36.1995
None of my containers in any layouts that functioned 2 weeks ago are working. No one has modified the DB in anyway since there. New containers are doing the same thing.
My container fields are only designed to exports PDFs.
files accessed through the filemaker pro on a mac on the local network do open. i will try filemaker pro remotely when I get home tonight.
The strange thing is i have scripts that email the container that work. my open in preview scripts are exactly the same accept the check box to automatically open is checked instead of email as attachemtn
This is my export script.
Set Variable [ $$FileName; Value:"tempdoc.pdf" ]
Set Variable [ $$FilePath; Value:Get ( TemporaryPath ) & "/"& $$FileName ]
Export Field Contents [ Inventory_Wiki::Doc photo; “$$FilePath”; Automatically open ]
Try using the Get (DocumentsPath) or Get ( FilePath)
You also don't need the "/"
A possible workaround would be to remove the "automatically open" option and follow it with Open URL.
The strange thing it that this functioned perfectly for over a year and nothing in my DB changed. I tried it from home on filemaker go and it works fine. All of JPs suggestions worked the same as my original script. I don't know what would cause FMGO to suddenly stop accessing the files on port 80 instead of 16000 as it always has. I am going to contact my ISP again and make sure nothing is blocked.
Don't see how
Set Variable[$$FilePath; Value:Get ( TemporaryPath ) & "/"& $$FileName]
Ever worked. That extra "/" should produce an invalid file path.
It does not appear to function without it the "/"
That makes no sense.
Get ( Temporarypath ) returns text ending in a /. Adding a / gives you an invalid file path. as you get that character doubled at the end of the text returned by Get ( TemporaryPath).
got it. that still does not change that my container container issue.
so.... i rebooted my server. it works now. wtf. thank you all for taking the time to respond.