Open charlied57 opened 10 months ago
Any body deploy success?
Your callback domain should be the same as what you have in your Homepage URL. This would be a great note to add in the documentation.
@charlied57 This isn't a Tabby Web issue. Cloudflare proxies only work on ports 80 and 443. What you need is to throw a reverse proxy in front of Tabby Web that will redirect traffic from domain.name:80/443 to container port 9090 so that ports 80 and 443 can be used.
I suggest looking into nginx reverse proxy or Traefik
I am having some issues getting tabby-web to deploy correctly using docker-compose, below is my config file. (Replaced variables with dummy data)
I do not have the connection gateway set up but will focus on that after setting up tabby-web.
I am including the GitHub environment variables here while I get it working and will move those later.
I have a MySQL server running at
192.168.1.210
with the usertabby
and the DBTabby
Within that DB I can see that the connection is successful because It has been populated with tables. When I boot the container the logs that it produces are:In the github OAuth settings I have the following (replaced domain name):![image](https://github.com/Eugeny/tabby-web/assets/42820941/29ab8a43-bd83-477c-a585-61e2366e7aae)
When I navigate to the local URL
192.168.1.211:9090
I receive aFirefox can’t establish a connection to the server at 192.168.1.211:9090.
When I navigate to the URL through the domain name I get the following error:![image](https://github.com/Eugeny/tabby-web/assets/42820941/65d345b7-c104-44a0-a815-7e41aa5bc70e)
The domain is set up through a Cloudflare tunnel that takes my domain name and directs it to
192.168.1.211:9090
. I don't have the full callback URL set up through the tunnel assuming that that is caught and forwarded by the domain name.So my question is, what am I setting up incorrectly? I thought I had set everything up that I needed. I can provide any additional information. Thanks for any help.