voyz

Great 👏 I'll let you know when it gets fully released. Thanks for adding your comment on the security concern. I'll leave this open for some time to let others...

I'm going to close this Issue as it is now released in `voyz/ibeam:0.5.4`. Let me know if you'd like to reopen it and continue the discussion. Thanks for contributing 👍

Hey @partakpavel @podoliako thanks for your patience, I was travelling over the past few weeks 🙏 Can you try the solution proposed here and let me know if it helps:...

@jetsondavis-genesis thanks for sharing this. Can you indicate if this persists if you try the solution I propose in my previous reply?

I'm going to close this issue due to inactivity. Thanks for your contribution and please feel free to request a reopen if you'd like to continue the discussion 👍

Hey @fortnumxy thanks for trying out IBeam and describing your issue in detail 👍 Where is this IBeam instance deployed? On a remote servers somewhere? Possibly the difference is due...

I'm going to close this issue due to inactivity. Thanks for your contribution and please feel free to request a reopen if you'd like to continue the discussion 👍

Hey @bbbbho thanks for sharing your issue - could you please post the full debug log from IBeam? We need to first verify that it can read this config file.

@bbbbho see: https://docs.docker.com/reference/cli/docker/container/logs/

Your conf.yaml is not recognised, otherwise you'd see `'Custom conf.yaml found and will be used by the Gateway'` printed. Please ensure it is provided through the inputs directory: https://github.com/Voyz/ibeam/wiki/Gateway-Configuration