# Access MeltingSpot ## Web browsers MeltingSpot is compatible with all currently supported web browsers. However, we highly recommend using Google Chrome, which happens to be our developers' top pick! 🌟 For the best experience, we suggest steering clear of outdated browsers like Internet Explorer. Trust us, your browsing journey will thank you! 🙏 ## Receive emails from MeltingSpot To ensure that MeltingSpot emails land safely in your inbox & avoid getting lost in the spam box, it's essential to whitelist our email domain (`app.mltngspt.com`) by your email client. Here are a few details to help you make sure our emails find their way to the right side of your mailbox: * Host: smtp.postmarkapp.com * Port: 587 * Addresses: and ## Firewall settings Our platform relies on various services that need to be accessible whenever you connect to your Spot. Here are the domain names we use to ensure everything runs smoothly: * `*.meltingspot.io` * `mltngs.pt` * `iframe.ly` and `iframely.net` * `daily.co` * `api.video` * `pusher.com` * Any domain related to resources you would like to use on the platform. eg: * `youtube.com` * `vimeo.com` * `drive.google.com` * ... To guarantee access to all features, please ensure that these domain names are authorized by your organization. * Make sure these domains are accessible. * And make sure that WebSockets are allowed on any of these domains and sub-domains on ports 80 and 443. Our video solution relies on Daily.co which has its own recommendations:
Daily.co settings Daily uses a variety of domains, IP addresses, ports, and protocols to connect calls. If you're trying to make calls to and from a network behind a corporate firewall, or through a VPN, you'll need to make sure you can access the following domains: * `*.daily.co` if possible. If not, you'll need to be able to reach these domains in addition to your account's `subdomain.daily.co`: * `[b.daily.co]()` and `[c.daily.co]()` for javascript, images, sounds, and fonts * `[gs.daily.co]()` for room status updates * `*.wss.daily.co` for SFU media connections. The first hostname will usually resemble an AWS IP, such as [`ip-172-31-10-133-ec2.wss.daily.co`](http://ip-172-31-10-133-ec2.wss.daily.co/). * `prod-ks.pluot.blue` (a Daily-owned server used for ICE negotiation) * `*.twilio.com` (STUN server/TURN relay for coordinating peer-to-peer calls) * `*.xirsys.com` (STUN server/TURN relay for coordinating peer-to-peer calls) Additionally, you'll want to make sure you can access `*.daily.co` on port 443, as it's used for a variety of fallback connection types. If you have a VPN, Daily calls will have much better quality if you can configure Daily's traffic to bypass it. You can usually do that by configuring split tunneling. You'll at least want to exempt port 443 for the Twilio IP ranges listed below, and possibly for the Xirsys IPs as well. If you can exempt UDP traffic altogether, that's even better. Twilio's IP ranges: Xirsys's IP ranges: If you have a firewall, you should allow UDP hole punching, which is essentially the standard behavior for most firewalls. If you're explicitly allowing or denying UDP ports, you'll definitely need to open port 3478 for signaling and media tunneling. You'll also need to open UDP ports 40000-65534 for all hosts in order for peer-to-peer calls to work correctly. If you have a network appliance that provides threat-based IP whitelisting/blacklisting (such as Cisco Talos), you may run into occasional connection issues based on your blacklist entries. Daily uses Amazon public cloud resources, so our call servers get assigned random IPs from Amazon’s address range. Occasionally, these IPs make it on to security blacklists because hackers use AWS too. When this happens, your users may experience some of the issues described in this document. Source:
## Blocked? No time to wait for IT support? Here's a quick fix: if you're trapped by IT restrictions and don't have time to contact your network administrator, here we've got you covered with a temporary workaround: * Share your smartphone's Internet connection and connect to your laptop using this connection. * Access the platform from your smartphone. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.meltingspot.io/english/how-to/access-meltingspot.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.