My shiny app works locally but shows "Disconnected from the server" when deploying. Is issue related to using Julia?

I'm having an error when trying to deploy my Shiny app. It runs locally, but whenever I republish and try to access it through the link, within seconds the screen is greyed out and "Disconnected from the server" appears. I have looked through the logs and have this message:

/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/local/julia-1.0.2/bin/../lib/julia/libLLVM-6.0.so)

My app uses Julia, so I'm wondering if the error is related to this. Does anyone know how I might go about fixing this problem?

Hi Alison,

Were you able to figure this out? May be having a similar problem, and there's not a whole lot of literature on this subject.

Thank you for reporting this, and I am sorry for the inconvenience.

The version of libc++ might be too old for Julia right now:

$ ldd /usr/local/julia-1.0.2/lib/julia/libLLVM-6.0.so
/usr/local/julia-1.0.2/lib/julia/libLLVM-6.0.so: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/local/julia-1.0.2/lib/julia/libLLVM-6.0.so)
        linux-vdso.so.1 =>  (0x00007ffdd42b7000)
        /lib/x86_64-linux-gnu/libSegFault.so (0x00007ff6429d7000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007ff6427cf000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff6425cb000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ff6423ae000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007ff64202c000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff641d23000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ff641b0d000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff641743000)
        /lib64/ld-linux-x86-64.so.2 (0x00007ff645878000)
$ strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_3.4.20
GLIBCXX_3.4.21
GLIBCXX_DEBUG_MESSAGE_LENGTH

I will file an issue to track this, but no guarantees for a timeline.