SuperContainer Access Error

[IT_User]

Hello,

 

So I had help setting up SuperContainer on a Mac FM Server.

 

If you go to (example) http://address.domain.com/SuperContainer/ it seems like anyone can access that.

However, when you go to the specified file, whether in FileMaker or in a browser it cannot reach it outside the network.  (The port I am using is 8080, and 8020 does not seem to work better.)

http://address.domain.com:8080/SuperContainer/File/Folder/filename.pdf

 

Do you know if it would be a problem where I am saving these files or something else? I'm not sure I understanding how this works.

 

I need other people from IWP in a webviewer to upload a file into FileMaker from anyone/anywhere without having them connecting to our network.

(There are other securities in place to access this layout, but after those are passed this should work, I hope.)

 

I appreciate any help I get.

Thank you

 

 

I have another problem after that, but I don't think it exactly relates.

[IT_User]

Contacted 360Works, and this was their reply

 

If you had SuperContainer installed onto FM Server then you shouldn't need to supply a port number in your URL. It should just be "http://address.doman/SuperContainer/Files/...". However if you are sure that you have assigned a custom port to SuperContainer then that's fine to include.

 

The URL used to access SC files starts with a base URL and is followed by the folder path pointing to the file on the server. So let's say you have a file at "my/custom/path/". You start with the base URL of "http://address.domain/SuperContainer/Files" and add the folder path to get the complete URL of "http://address.domain/SuperContainer/Files/my/custom/path". 

 

The solution you mention at the end of your post should work fine. You shouldn't have a problem having a web viewer in your IWP database file that lets people upload files.

 

 

I have another problem after that, but I don't think it exactly relates.

 

 

I changed it to not have a port (so it defaults to 80), and I get the files saved, but not where I had originally intended.  The only thing I need to test now is if other people can, as well.  (I also had to play around with folder permissions, as it didn't let the filemaker server account to save.)