Ticket: Localhost Config Error with X and LinkedIn Integration
@KevinUK Just created a ticket
Question: Unable to get X or LinkedIn working with localhost.
Attempted: I'm running localhost and got to the add channel popup. I've added postiz.env in the same dir as docker-compose.yml. I've followed the tutorials for each provider but with X I get 'could not connect to the platform' and LinkedIn is passing in client_id undefined so I'm guessing it's a config issue. https://www.linkedin.com/oauth/v2/authorization?response_type=code&client_id=undefined&xxxxx When I set the .env values I stopped and started the postiz docker container. Any tips on where I am going wrong? Thanks!
Working On: Configuring channels
Using Postiz On: docker-compose
Take it from here @Postiz
Question: Unable to get X or LinkedIn working with localhost.
Attempted: I'm running localhost and got to the add channel popup. I've added postiz.env in the same dir as docker-compose.yml. I've followed the tutorials for each provider but with X I get 'could not connect to the platform' and LinkedIn is passing in client_id undefined so I'm guessing it's a config issue. https://www.linkedin.com/oauth/v2/authorization?response_type=code&client_id=undefined&xxxxx When I set the .env values I stopped and started the postiz docker container. Any tips on where I am going wrong? Thanks!
Working On: Configuring channels
Using Postiz On: docker-compose
Take it from here @Postiz
2 Replies
Got it working but have a suggestion.
I had not played with .yml files before and realised the api keys/values go in docker-compose.yml under the environment section within postiz.
https://docs.postiz.com/providers mentions a .env file which lead me down the wrong path.
Maybe update the docs with this info or include commented out values for the channels in the .yml? I would have spotted what needed doing as had started off in the .yml file.
Hi @KevinUK Please select an action
The thread is now closed