Fresh vesta install, can't access for some reason

[Botanist_]

Hello!
I've just installed fresh debian 7 server and installed vestacp.
Installation was successful but for some reason I can't connect to it.
https://panel.mydomain.tdl:8083 doesn't work. Can cloudflare be the problem?
Thank you!

[mehargags]

try accessing it with your IPv4(s)

[dpeca]

Hm, yes, CloudFlare is masking your real IP, and, actually, you are trying to connect to CloudFlare server at 8083 port.
Hostname of your server should NOT be filtered via CloudFlare.

[dpeca]

It's not DNS propagation if he check cloud icon in DNS zone editor.
If he check it, CloudFlare will not point to his real IP, but to it's own (CloudFlare) proxy server.
So, when he try to open http://his-hostname.com:8083/ it will not reach his server, but cloudflare proxy server, that will not pass connection to his real IP.

[mehargags]

When you are opening the IP with http://<IP> how can any DNS or cloudflare service interfare ? IP is direct address, he should have the access unless the server has firewall filtering.

[dpeca]

he is not opening IP but hostname that is probably firewalled by CF.

[dpeca]

I did NOT said that he can not access Vesta via https://HIS-REAL-IP:8083/ :D

I said he can not access Vesta via https://his-hostname.com:8083/ if he put his-hostname.com on CloudFlare and TURN ON CloudFlare caching for that A record.
Because, in that case, when he try to open https://his-hostname.com:8083/ TCP connection will go to CloudFlare server.
CloudFlare server will drop it.
And that is the end.

And I also said this issue IS NOT related to DNS propagation.

And of course - he can access Vesta via https://HIS-REAL-IP:8083/

[dpeca]

OK... then I hope he did not put CloudFlare proxy on 'panel' A record... because if he did, then the point is the same as I described.

[dpeca]

Cloudflare will pass TCP connection on port 8083 to real IP ?
Are you sure?

They are not passing SSH nor FTP connection (nor SMTP, POP3, IMAP), so I believed they drop all ports except http port 80 and https port 443.

[dpeca]

I'm not sure you are reading my posts.

I'm talking ONLY and ONLY about case when you TURN ON cloudflare reverse proxy on some hostname - and then you try to access that hostname on 8083 port (or any other port except 80 and 443) - I'm telling you it WILL NOT pass connection to REAL-IP.

Do you want that we make a test - I will put one domain behind clodflare reverse proxy - and you try to reach port 8083 on that domain?