Frequently Asked Questions

📚Contents (Click to Jump)#

1. Playback Stuttering
2. Emby Login Troubleshooting Guide
3. Search Problems
4. Media Problems
5. Playback Says “No Compatible Streams”
6. Other

1.🌀Playback Stuttering#

Playback stuttering is a common issue. Start by checking two main factors:

1. Server performance and load
2. The network route used to reach the Emby server

When the server is running normally, is not under attack, and has low network load, the network route is usually the main factor affecting playback.

If a direct connection is unstable, try connecting through a proxy. Network conditions in mainland China vary widely, and the routes offered by a server may not work equally well for everyone. Peak-hour traffic can also affect connection quality.

A proxy gives you more routes to choose from. If several nodes are available, switch based on actual playback performance. Proxy connections can also fluctuate.

In addition, a video's bitrate also affects playback smoothness. Emby servers may collect media without a bitrate ceiling, including a great deal of 4K and high-bitrate content. A 5 Mbps file and a 20 Mbps file have very different network requirements. Before opening high-bitrate content, make sure your network can handle it.

Finally, if playback is not smooth:

• First, check whether the server load is within the normal range. If the load is abnormal, report it to the server owner.
• If server load is normal, try different routes and nodes. Node speed tests and YouTube playback speeds do not necessarily reflect the connection to Emby, and expensive proxy services can still fluctuate. Use actual playback performance as your guide and switch routes as needed.

🔧 Emby Login Troubleshooting Guide#

If Emby cannot connect, sign-in fails, or an error code appears, use the guide below to narrow down the cause.

Error messages can vary across clients, reverse proxies, and Cloudflare setups, so a code is only a starting point. If no code is shown, go straight to the quick troubleshooting steps.

Quick error-code reference

Code	Check first
400, 404	Address, path, current route
401	Account, password, old Token
403	Permissions, IP, security rules
405, 501	Client support, proxy settings
408	Request timeout, network
410	Removed resource, old server entry
429, 1015	Stop retrying; wait for rate limits
500, 503	Server errors, maintenance, load
502, 504	Proxy and upstream Emby service
520–524	Cloudflare-to-origin connection
525, 526	Origin TLS and certificate
530, 1000, 1001, 1016	Full Cloudflare error and DNS
1020 / Access Denied	Cloudflare access rules

📱 Client / HTTP 4xx Errors#

400 Bad Request | Invalid request

Possible causes include a malformed server URL, invalid client parameters, or a reverse proxy changing the request.

Check the complete address, for example https://example.com. Remove extra spaces, incorrect paths, and duplicated http / https prefixes. Include a port or subpath only if the server owner supplies it. Fully quit and reopen the app after checking the address.

401 Unauthorized | Authentication failed

The request lacks valid credentials. Common causes include an incorrect username or password, an expired Token, saved old credentials, or a password reset on the server.

Enter your current username and password manually. Avoid relying on saved login details. If necessary, remove the server entry from the client and add it again. If you forgot your password, use the owner's bot or designated reset channel.

403 Forbidden | Access refused

Possible causes include a disabled account, an IP ban, missing resource permissions, reverse-proxy restrictions, or Cloudflare WAF / security rules.

Open the server address in a browser. If the webpage also returns 403, the problem is usually not limited to the app. Ask the owner to confirm account status or investigate a persistent security block, using the complete error message.

404 Not Found | Address or resource not found

Check for a misspelled domain, an outdated route, a nonexistent request path, or incorrect reverse-proxy path configuration.

Obtain the current address from the bot or announcements. Do not add API paths yourself. If the correct homepage loads but one feature returns 404, report the specific action to the owner.

405 Method Not Allowed | Request method not accepted

The resource does not accept the HTTP method used by the client. Possible causes include client compatibility problems, incorrect Nginx rules, or a Cloudflare Worker rewriting the method incorrectly.

Try adding the server again and check client compatibility. If several users are affected, the administrator should check the proxy and request methods.

408 Request Timeout | Incomplete request timed out

In HTTP, this means the server did not receive a complete request within its waiting period. An app displaying “connection timed out” has not necessarily received an actual HTTP 408 response.

Unstable networks, poor cross-border routes, or busy services can affect requests. Compare Wi-Fi and mobile data. If many users are affected, ask the owner to check the service and network route.

410 Gone | Resource unavailable / old server entry checks

The standard HTTP meaning is that the resource is no longer available at the origin and this is likely permanent.

In some Emby or third-party clients and particular service environments, a 410-like message may also accompany an outdated address or problematic saved server entry. Users of this site can try completely removing that server entry from the client, then adding the latest address again.

This is a troubleshooting step, not an official fixed Emby definition of 410. If it continues, ask the owner whether the resource or route has been retired.

429 Too Many Requests | Rate limit reached

Possible causes include rapid sign-in attempts, repeated refreshes, Cloudflare Rate Limiting, server limits, or a shared IP exceeding a limit.

Stop retrying and wait a few minutes. Follow the waiting time shown on the page if one is provided.

🔧 Server / Reverse-Proxy 5xx Errors#

500 Internal Server Error | Internal failure

A service processing the request encountered an internal error. It may involve Emby Server, a plugin, server software, or a proxy backend. A 500 alone does not establish a local network fault.

Try again later. If others see it too, the administrator likely needs to inspect server logs.

501 Not Implemented | Unsupported functionality

This uncommon response means the server does not support functionality needed to fulfil the request. Server components, proxy settings, or client compatibility may be involved.

Check the client version and report the exact action if the error persists.

502 Bad Gateway | Invalid upstream response

A gateway or proxy did not obtain a valid upstream response. Common Emby-related causes include a stopped service, an incorrect Nginx upstream address or port, and an origin outage. Cloudflare can also generate a 502.

Wait 2–3 minutes and retry. Persistent errors need an administrator to check the proxy and origin.

503 Service Unavailable | Temporarily unavailable

Possible causes include a restart, maintenance, overload, or an unavailable upstream service. Emby, a proxy, or a CDN may return the response.

Check announcements and try later. Follow any suggested retry time.

504 Gateway Timeout | Upstream response timed out

The proxy did not obtain a timely response from an upstream service. A timeout can occur while connecting or waiting for a response; the code alone does not prove the connection succeeded.

Common causes include a stalled Emby service, high load, a slow upstream, or network-route problems. Wait 2–3 minutes before retrying and report persistent failures.

☁️ Common Cloudflare Errors#

These describe problems between Cloudflare and the origin. Ordinary users usually cannot fix the origin configuration. Check maintenance announcements or test another route already supplied by the owner.

520 Web Server Returned an Unknown Error | Unexpected origin response

The origin returned an empty, malformed, or unexpected response. Wait about 30 seconds, then refresh once. Report persistent errors to the administrator.

521 Web Server Is Down | Origin refused the connection

The origin refuses Cloudflare's connection. The origin or Nginx may be stopped, or a firewall may block Cloudflare. The owner normally needs to resolve this.

522 Connection Timed Out | Origin connection timeout

Cloudflare timed out contacting the origin. This may happen during TCP establishment or while awaiting acknowledgment after connection. Firewall drops, network problems, or an overloaded origin are possible causes.

Try later and contact the owner if it continues.

523 Origin Is Unreachable | Origin cannot be reached

The origin is unreachable, usually because of an incorrect origin IP, routing, or network problems. The administrator should check the origin address in DNS and network reachability.

524 A Timeout Occurred | Origin response timeout

Cloudflare connected to the origin, but an HTTP response did not arrive in time. Some cases involve a timeout while writing a request to the origin. High Emby load, stalled software, or long processing times may contribute.

Retry later and report recurring errors.

525 SSL Handshake Failed | Origin TLS handshake failed

The TLS handshake between Cloudflare and the origin failed. An administrator must check origin HTTPS, ports, certificates, and TLS settings.

526 Invalid SSL Certificate | Origin certificate validation failed

Cloudflare cannot validate the origin certificate. In Full (strict) mode, common causes include an expired certificate, a hostname mismatch, or an incomplete certificate chain.

The administrator should check certificate validity, hostname, chain, and the Cloudflare SSL / TLS mode. While repairs are underway, users may test another server route already provided by the owner.

530 Cloudflare Error | Read the specific 1xxx message

530 is the outer HTTP status. In common Cloudflare cases it involves failure to resolve the origin hostname, and the response body contains a more specific 1xxx code.

Do not reduce every 530 to “DNS error.” Record the full Cloudflare Error Code and follow its explanation.

Error 1000 | DNS points to prohibited IP

A DNS record points to an IP Cloudflare does not permit for proxying. Proxy loops or related configuration issues can also be involved. The administrator should check DNS and proxy configuration.

Error 1001 | DNS Resolution Error

A Cloudflare-related DNS lookup failed, for example an unresolvable CNAME target. Confirm the server address, then ask the administrator to check DNS records.

Error 1015 | You Are Being Rate Limited

Requests triggered the site's Cloudflare rate-limit rules. Stop refreshing and wait a few minutes, or for the time shown on the page.

Error 1016 | Origin DNS Error

Cloudflare cannot resolve the origin address. The administrator needs to check relevant origin A / AAAA / CNAME records and related DNS settings.

Error 1020 / Access Denied | Security rules refused access

1020 normally concerns a Cloudflare firewall-rule denial. Other Access Denied messages may come from WAF or access-control policies; read the complete page.

Disable a problematic proxy, compare networks, and test later. Contact the owner if it persists. Messages vary across products and newer error pages; not every security block displays 1020.

DNS / HTTPS / Local Network Problems#

“Server not found” or DNS lookup failure: Check the domain spelling and latest announced address, then compare networks. Failure on one network may involve local DNS, the router, or the ISP; failure across networks may involve the domain or server-side DNS configuration.

“Invalid certificate,” “connection not private,” or SSL errors: Check automatic date, time, and time-zone settings, and confirm the hostname. Expired or mismatched certificates require administrator action. Do not bypass a browser certificate warning to enter your password.

The browser works but the app fails: Check the app version, old Token, cache, and saved server entry first. A working homepage does not prove that the login API or every app request works.

⚡ Quick Troubleshooting Steps#

1. Refresh once / fully quit and reopen the Emby app. If a rate limit is shown, wait instead of retrying repeatedly.
2. Check the server address. Confirm http / https, domain spelling, and the latest route from the bot or announcements. Do not add extra paths; use ports and subpaths only as specified by the owner.
3. Switch networks. Compare Wi-Fi and mobile data.
4. Test with the proxy / VPN disabled. This helps identify proxy-route problems. For routes requiring a proxy, also compare another working route supplied by the owner.
5. Open the server address directly in a browser. If that also fails, the issue usually extends beyond the app.
6. Use a private / incognito window. This helps exclude ordinary-window cookies and saved sign-in state; it does not automatically fix DNS, networking, or certificates.
7. Check the device date and time. A badly incorrect clock can break HTTPS certificate validation.
8. Enter your current credentials manually. Avoid old passwords and autofill. Use the designated reset channel if needed.
9. Remove the client-side server entry and add it again. Useful for stale cache or Tokens, server migrations, and route maintenance. This does not delete your server-side account.
10. Restart the device. This can resolve some cache, network-state, or client problems.
11. Check whether only you are affected. Use announcements and other users' reports rather than a single failed attempt.

💡 Locating the Fault#

If the issue remains, provide the owner with the full error code, time and time zone, client name and version, whether others are affected, and the networks tested. Include the Cloudflare Ray ID if displayed. Hide passwords, Tokens, and personal details in screenshots, and do not disclose the server address in public groups.

Technical references: HTTP status codes (RFC 9110), 429 (RFC 6585), Cloudflare 5xx, Cloudflare 1xxx.

3.🔍Search Problems#

Emby search, especially Chinese search, has some limitations, although individual servers may have made improvements. If you encounter a problem, send the developers specific feedback to help improve search.

Here are some search tips:

• Chinese keyword searches require at least two characters
• For a one-character Chinese title, search for the title followed by a comma. For example, “咒,” will find 《咒》
• If a Chinese search returns no results, search in the title's original language
• Chinese titles follow TMDB metadata
• If TMDB metadata lacks a Simplified Chinese translation, try Traditional Chinese keywords
• In movie libraries, sort by date added to find newly added movies more easily
• In TV libraries, sort by date last episode added to find newly updated series more easily

4.📦Media Problems#

After a channel announces an item, it still needs to be downloaded, organized, and added to the library. The announcement time is therefore not the same as the time it becomes available in Emby.

📺 TV Episodes Announced in the Channel (Excluding Current-Season Anime)#

Process: Announcement → Download and upload → Add subtitles → Add to library → Scrape metadata → Appear in Emby

Content that remains unavailable in Emby for a long time is often a British or American TV series, usually because it is waiting for subtitles. Subtitle availability depends on when subtitle groups release them. We will not add lower-quality hard-subtitled versions merely for speed, nor will we use scripts to add machine-translated subtitles. Please be patient.

🎬 Movies Announced in the Channel#

Process: Announcement → Download and upload → Scrape and add to library → Appear in Emby → Add non-machine-translated subtitles when a subtitle group releases them

Unlike TV series, new movies are added directly whether or not Chinese subtitles are available. Non-machine-translated subtitles will be added later. We also encourage everyone to share non-machine-translated subtitles with the server owner to improve the Emby server experience.

❗Important#

• Every stage takes time. When you see a resource announcement in the channel, please wait patiently
• When many items are added at once, scanning and organizing them may take time. An item may not appear until the relevant scan has finished
• Read the guidance before asking questions. Repeated uninformed comments or unreasonable demands may result in the loss of posting privileges in the channel and group
• Emby servers do not add movies that are currently showing in mainland Chinese cinemas. We sincerely recommend supporting them in theaters
• Asking for movies that are still in theaters may cause you to lose permission to speak in the channel and group, or even be banned
• Streaming releases, high-definition recordings, and Blu-ray remuxes or encodes are the only sources used by Emby servers. Low-quality prereleases, cam recordings, and low-quality hard-subtitled files are not accepted
• Before asking, confirm that the content has been released through one of the channels above

5.🚫Playback Says “No Compatible Streams”#

• Most browsers cannot decode HEVC (H.265) 10-bit video, so this message appears. Use a client app for playback (most Emby servers now prohibit browser playback)
• If this message appears in the official Android client, restart the app and try again
• If this message keeps appearing in a client app, report it to the server owner with the client version, the media you tried to play, and the exact error

6.❓⋯Other#

Protect your privacy when using Emby. Keep the following points in mind:

• Avoid using your real name with Emby
• Do not use the photo-upload feature!
• Do not disclose an Emby server's service address publicly. Attacks against an Emby server seriously affect everyone's experience. Publicly leaking the address will result in your account being banned