Jump to content

Conner360Works

360Works
  • Posts

    3
  • Joined

  • Last visited

Profile Information

  • Title
    Junior Developer
  • Industry
    Software Development

FileMaker Experience

  • Skill Level
    Novice
  • Application
    19

Platform Environment

  • OS Platform
    Mac
  • OS Version
    Big Sur

Claris Partner

  • Certification
    Not Certified

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Conner360Works's Achievements

Newbie

Newbie (1/14)

  • Dedicated Rare
  • One Month Later
  • Week One Done
  • First Post

Recent Badges

0

Reputation

  1. Hi Peter, No that is quite alright, your response was not received harshly at all! We would recommend installing and using Apache web server, this will handle the ssl connections. You will need to install an ssl certificate into that web server. Then you would need to configure Apache to forward requests to zulu. Below are the rules are installer writes to the Apache config file when you run the installer in FileMaker Server and you will be doing the same thing just manually. #zulu begin ProxyPass /zulu ajp://127.0.0.1:42424/zulu retry=1 timeout=7200 Redirect /.well-known/caldav /zulu/.well-known/caldav #zulu end You will need to add the above rules manually to your Apache configuration file. Here is a link to some helpful documentation in regards to Apache and setting up ssl connections, specifically focusing on the Forward Proxies and Reverse Proxies/Gateways section. https://httpd.apache.org/docs/2.4/mod/mod_proxy.html Regards, Conner Mcauliffe 360Works Support Team
  2. Hi Peter, I would like to get a little more information on your setup, are you using Apache as your web server? If not, what server are you attempting to use for you custom installation? Regards, Conner McAuliffe 360Works Support Team
  3. Hi Ruben, When working with very large files or amounts of data, the plugin may run out of memory. Follow this link http://docs.360works.com/index.php/Heapspace_Out_of_Memory_Error for more information on headspace errors and steps to take to increase it. By default, 360Works plugins use 256 MB headspace for the JVM to run the code. I would recommend trying to increase to 512MB first and seeing if that solves the issue and if more memory is needed increasing it to 1024 MB. If the problem persists, please send an email to support@360works.com along with your log files so that we can assist you further. More information and assistance on where to find logs and how to report them can be found here. Regards, Conner360Works
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.