Pavel Boger

Ab Fahmy thanks for the question. Based on the symptoms you describe, Space just can't access your private network as it's probably not exposed to the internet. There's no way to work around this i...

1. Community
2. General Discussion
3. connecting jetbrains space cloud instance to teamcity on-prem installation

• 0 votes

Thanks for the question. Please note that mailhog is not a real SMTP server that sends emails to the end users. Instead, it's a handy tool to intersect emails sent by the Space installation itself....

1. Community
2. General Discussion
3. ON-PREM: Mail not working.

• 1 vote

Jens Bosse, may I ask if you tried to delete the installation data and check if the error still occurs? (you can run docker compose -p space-on-premises down -v, but note that it will delete all th...

1. Community
2. General Discussion
3. How to Setup Spaces with only IPs (no domain names)

• 0 votes

Davidmirv, Dmitry Ivanoff  I apologize for the inconvenience caused. The new version with the fix is already on its way to production. Please stay tuned. 

1. Community
2. General Discussion
3. Elastic unauthorized errors in Space on-premises k8s pod

• 1 vote

Thanks for the question! May I ask if you tried the approach described in this article?

1. Community
2. General Discussion
3. How to access private container registry images with a token?

• 0 votes

Thanks for this information! May I ask if you tried to clear the cache and other site data? Are there any other extensions enabled for your default browser?

1. Community
2. General Discussion
3. On Premise: After setting up production web returns "Connection to server timed out"

• 0 votes

Jan Zenisek thanks for reporting this! Could you please share the entire logs from all Space containers? Please also share your nginx configuration if it differs from the one provided in our guide....

1. Community
2. General Discussion
3. On Premise: After setting up production web returns "Connection to server timed out"

• 0 votes

Techadmin, right, it should be like this: circlet {...    packages {        internalUrl = "http://packages:9390"        ...        }    }  

1. Community
2. General Discussion
3. Space not starting up after production configuration

• 0 votes

Techadmin I believe you unintentionally removed a `circlet.packages.internalUrl = "http://packages:9390"` from the `space.on-premises.conf` file. Could you put it back and try to start Space again?

1. Community
2. General Discussion
3. Space not starting up after production configuration

• 0 votes

Techadmin, thanks for reaching out to us! You're right, as you're getting a 5** error, it's necessary to check if Space works as expected. For this, let's access the logs: 1. get the IDs of Space-r...

1. Community
2. General Discussion
3. Space not starting up after production configuration

• 0 votes